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.

Note: <strong>IBM</strong> HTTP <strong>Server</strong> for z/OS offers the unique feature of a scalable mode.<br />

This allows the server to start additional instances of itself to offer vertical<br />

scalability if the performance goals are not met.<br />

DMZ secure server<br />

The DMZ secure proxy provides horizontal and vertical scaling capabilities<br />

besides the scaling activities on a per server basis. When scaling vertically, make<br />

sure that you have sufficient resources. Also, be aware that this provides only<br />

limited high availability. In any scaling scenario you need an IP sprayer like the<br />

Edge Components to spread the incoming traffic across all proxy servers.<br />

<strong>WebSphere</strong> containers<br />

Scaling at the application server layer can be done with vertical or horizontal<br />

scaling, or both. Vertical scaling at the application server layer can be done<br />

physically or logically. <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> is a Java application itself<br />

and can take advantage of additional processors or memory in the machine.<br />

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> applications can be clustered vertically, providing<br />

multiple copies of the same application on the same physical machine.<br />

<strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> also supports horizontal cloning of applications<br />

across multiple machines, which do not need to be identical in terms of physical<br />

resources.<br />

Default messaging<br />

With the messaging engine and the service integration bus, <strong>WebSphere</strong> offers<br />

the ability to scale messaging resources more efficiently. Using a cluster as a<br />

service integration bus member, you can create partitioned destinations. This<br />

enables a single logical queue to spread across multiple messaging engines. In<br />

this scenario, all messaging engines are active all the time. For n cluster<br />

members, the theory is that each receives an nth of the messages. This allows<br />

for greater scalability of messaging resources across the cell. One key factor to<br />

consider in this design is that message order is not preserved. That may or may<br />

not be significant, depending on the nature of the application.<br />

Multiple messaging engines for a cluster bus member is not the default setting.<br />

For workload management, you must take steps to add additional messaging<br />

engines. To make sure that the messaging engines are really running on different<br />

servers you must configure proper high availability policies. <strong>WebSphere</strong><br />

<strong>Application</strong> <strong>Server</strong> V7 features a wizard for high availability policy setup which<br />

can be used for most topologies.<br />

234 <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!