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.

Different file systems for the following purposes are useful:<br />

► <strong>Application</strong> binaries<br />

This file system stores the product binaries as dumped by the installer. When<br />

designing this file system keep in mind that installing maintenance causes this<br />

file system to grow.<br />

► Profiles<br />

This file system stores the profile-specific data that defines your runtime<br />

environment. The minimum disk space required depends on the profile type<br />

you create. The amount of user data needed depends on the applications<br />

deployed to the profile.<br />

► Log files<br />

The purpose of this file system is to hold the log files of the application<br />

servers. If this file system is not mounted under the default mount point you<br />

have to change the server configuration for each server. This can be<br />

accomplished either through scripting or by using a custom server template.<br />

The size depends on the application and on the log retention policy of the<br />

application servers.<br />

► Dumps<br />

System core dumps and Java heap dumps can be large and quickly fill a file<br />

system. Therefore, it is a good practice to redirect system dumps, Java heap<br />

dumps, and the Java core dumps to a dedicated directory.<br />

This avoids a dumping process or Java virtual machine (JVM) filling up file<br />

systems and impacting other running applications. It also allows you to locate<br />

them easily. The size depends on the number of JVMs dumping to this<br />

directory, their individual sizes, the number of dumps you want to retain, and<br />

so on.<br />

► Maintenance packages/CIM repositories<br />

For easier management of your installation packages and your fix packs or<br />

individual fixes you should keep them in a central repository. If you use the<br />

centralized installation manager (CIM), this repository is located on the<br />

deployment manager system.<br />

Note: You do not need this file system on every server. Just maintain one<br />

repository containing all your installation media, fixes, fix packs, and so on,<br />

to have all installables at hand in case you need them.<br />

► User data and content<br />

This file system should be used to store other user data and content being<br />

used in the applications.<br />

Chapter 6. Installation 183

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

Saved successfully!

Ooh no, something went wrong!