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

9.1 What is new in V7.0
The following list highlights the changes in administrative tools and processes in
WebSphere Application Server V7.0:
► Simplified administration of multiple Base profiles with an administrative agent
Prior to WebSphere Application Server V7.0, whether a Base or Express
installation, the WebSphere Administrative Console resided in the default
WebSphere Application Server. If you created multiple profiles within the
Base, each profile had a WebSphere Application Server instance and the
WebSphere Administrative Console resided in each WebSphere Application
Server instance. To administer each WebSphere Application Server instance,
you had to log into each individual WebSphere Administrative Console.
In WebSphere Application Server V7.0, you can use the administrative agent
to centrally manage all WebSphere Application Server instances within the
same physical server created by Base profiles. This is done through the
Integrated Solutions Console, where you select which WebSphere
Application Server instance to administer. This new feature reduces the
individual WebSphere Application Server footprint associated with
administration. It also simplifies administration of multiple Base profiles
WebSphere Application Server instances.
We discuss this more in 3.1.7, “Administrative agent” on page 63.
► Centralized administration of multiple WebSphere domains with a job
manager
In WebSphere Application Server V7.0, the job manager has been introduced
as a loosely coupled management model based on asynchronous
implementation, so that it provides centralized administration for multiple
deployment managers and multiple Base profiles (through an administrative
agent). It centralizes the distribution of applications, applications updates, and
WebSphere Application Server configuration updates across a large number
of WebSphere administrative domains. This dramatically increases the scale
of administration for WebSphere Application Server implementations. The job
manager does not replace deployment manager but augments it.
We discuss this more in 3.2.4, “Flexible management” on page 78.
► New runtime provisioning service
The new runtime provisioning service commissions only those components in
the Java Virtual Machine (JVM) that are required by the installed applications.
At application installation time, WebSphere Application Server examines the
application and creates an application-specific activation plan. At WebSphere
Application Server startup, it only starts those components that are detailed in
312 WebSphere Application Server V7.0: Concepts, Planning, and Design