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

Preparing the sysplex

About this task

WebSphere Application Server for z/OS uses a number of z/OS sysplex services. Therefore, each target system used to run WebSphere Application Server for z/OS must be either a monoplex (single system sysplex) or a member of a sysplex. For more information, see z/OS MVS Setting Up a Sysplex (SA22-7625).

Connect systems in a sysplex with channel-to-channel (CTC) communications or through a coupling facility, which is a special logical partition used to share data between sysplex members. Couple data sets on DASD are also used for sysplex coordination.

WebSphere Application Server for z/OS uses the System Logger, an MVS component that allows applications to log data in a sysplex, to log error and trace information and provide XA transaction logging. The System logger creates and manages log streams, which are written first to a coupling facility or local in-memory buffer, then transferred to log data sets on DASD for longer term access. Log streams that are written to local buffers rather than to a coupling facility are called DASD-only log streams.

Avoid trouble: [aug2010] If you are using a global resource serialization (GRS) ring to attach one or more monoplexes to a sysplex environment, the cell name of any servers running in any of the monoplexes must be unique within the entire GRS environment. This requirement means that the cell name of a server running in any of the monoplexes:
  • Must be different than the cell name of any servers running in the sysplex
  • Must be different than the cell name of any servers running in another monoplex that is attached to the sysplex
If you have servers with duplicate cell names within the GRS environment, WebSphere Application Server cannot differentiate between the sysplex cell and the monoplex cell, and treats both servers as part of the same cell, This inaccurate cell association typically causes unpredictable processing results. [aug2010]
aug2010
gotcha

Follow these steps to prepare your system for a sysplex.

Procedure

  1. Determine if your z/OS target system is already configured as a sysplex.
    1. If so, continue on to the next step.
    2. If not, follow the instructions in z/OS MVS Setting Up a Sysplex (SA22-7625) to configure it as a monoplex. Record the sysplex name for later use.
  2. Determine if System Logger is already in use on your system.
    1. If so, continue on to the next step.
    2. If not, follow the instructions in the section "Preparing to Use System Logger Applications" in z/OS MVS Setting Up a Sysplex (SA22-7625).
  3. Decide whether WebSphere Application Server for z/OS log streams should reside in a coupling facility or local in-memory buffers. Record the SMS data class, SMS storage class and data set name prefix to be used for log data sets. If WebSphere Application Server for z/OS log streams will reside in a coupling facility, choose the structure name to be used.
Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 8:25:23 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=tins_prepsysplex
File name: tins_prepsysplex.html