To successfully run an application on WebSphere Application Server running on System p, we need to consider all of the perspectives just described. Typically, your enterprise will have teams of specialists that bring a combination of skills in the following areas: AIX operating systems administration, System p hardware configuration and tuning, and Java and WebSphere application engineering.
Specialists focusing on each of these skill sets work from different perspectives within the whole system view, as shown in Table 1-2. As a result, the potential exists for confusion over terminology and overlapping functionality when you try to combine these viewpoints into a single, overall system optimization strategy.
The specialists tend to work at a single level; for example, a UNIX systems administrator will tend to see things from the operating system point of view, and a Java developer will tend to see things from the application programmer point of view. Table 1-2 lists system features and points of interaction at which the WebSphere Application Server and system administration viewpoints might integrate.
Table 1-2
| AIX | Java | |
|---|---|---|
| Dynamic Provisioning | Operating system images, NIM Server, Automatic Builds | Silent Install Scripts Installation Factory Restore from backup |
| Dynamic Resource Allocation | Micropartitions Entitlements (Service Level Agreements), Workload Management Priority/Weighting | Configuring new servers into a Network Deployment cell, WebSphere eXtended Deployment |
| Tuning Format | Operating system Tuning Bring up Runtime (part of load testing, and an ongoing activity) | JVM Tuning Operating system-specific WebSphere Application Server parameters? |
System viewpoints and integration