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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

14.8.1 Installation overview<br />

To install a <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> for z/OS <strong>V7.0</strong> on z/OS there are three<br />

major steps to be performed:<br />

1. System preparation<br />

2. Product code installation with System Modification Program/Extended<br />

(SMP/E)<br />

3. Product configuration, including the profile creation, using Job Control<br />

Language (JCL)<br />

14.8.2 Installation considerations<br />

This section includes general considerations when installing a <strong>WebSphere</strong><br />

<strong>Application</strong> <strong>Server</strong> for z/OS <strong>V7.0</strong>.<br />

General environment considerations<br />

Planing your environment is critical, so a dedicated chapter is introduced in this<br />

book. See Chapter 4, “Infrastructure” on page 93.<br />

Naming convention<br />

When installing <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> for z/OS <strong>V7.0</strong>, make sure you<br />

use a good naming convention. The operating system restriction to eight<br />

characters limits your naming convention to the usage of abbreviations. Keep in<br />

mind that there are new components introduced in <strong>WebSphere</strong> <strong>Application</strong><br />

<strong>Server</strong> for z/OS <strong>V7.0</strong> (for example the administrative agent and job manager).<br />

Make sure that your convention reflect this information as well.<br />

Note: The naming convention guidelines from the Washington System center<br />

are included in the configuration tool for the profile creation.<br />

Real memory defined<br />

Keep in mind that the <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> for z/OS has a different<br />

blueprint than <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> for distributed environments. See<br />

14.1.4, “Structure of an application server” on page 422 for more details.<br />

Because there are multiple heaps, one for every controller and servant region,<br />

this results in different memory requirements.<br />

It is absolutely critical that the heaps defined in a <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong><br />

environment fit into real memory. The impact of not having the heap in the real<br />

memory would be a negative performance impact due to paging during each<br />

Chapter 14. <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> for z/OS 457

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

Saved successfully!

Ooh no, something went wrong!