29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

While <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> profiles on z/OS are built using multiple<br />

building blocks, it is still a single instance of an application server from an<br />

application developer, system administrator, or user perspective. This means that<br />

nearly all <strong>WebSphere</strong> variables can be defined against a server, and are not<br />

defined against the servant and control region adjuncts. However some of the<br />

settings, like heap sizes have to be done for each of the components.<br />

All the possible profiles that can be instantiated, are built using the different<br />

regions:<br />

► <strong>Application</strong> server<br />

► Deployment manager<br />

► Job manager<br />

► Administrative agent<br />

Control region<br />

The control region is the face of the application server to the outside world. It is<br />

the only component that is reachable from the outside world using standard<br />

protocols and port communication. For communication with the servant regions,<br />

where the application is executed, the control region is the endpoint for TCP<br />

transportation and switches to WLM queues.<br />

Keep the following points in mind about control regions:<br />

► An application server can only have one control region.<br />

► The control region contains a JVM.<br />

► The control region will be start- and endpoint for communication.<br />

Servant region<br />

The servant region is the component of an application server on z/OS where the<br />

actual application is run and transactions are processed. The EJB and Web<br />

container are included here.<br />

As seen in Figure 14-2 on page 423, it is possible to have multiple servant<br />

regions per application server. (But only one for the other profile types.) This<br />

concept is called a multi-servant region or internal cluster. Through the usage of<br />

this technique, it is possible to actually benefit from cluster benefits without the<br />

overhead of a real cluster. For continuous availability and scalability, it is<br />

suggested to build a <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> cluster that integrates these<br />

mini clusters. While creating a normal cluster you can still use multiple servant<br />

regions for each cluster member.<br />

424 <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>: <strong>Concepts</strong>, Planning, and Design

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!