WebSphere Application Server Profiles V7

Types of profiles : The WebSphere Application Server installation process simply lays down a set of core product files required for the runtime processes. After installation, you need to create one or more profiles that define the runtime to have a functional system. The core product files are shared among the runtime components defined by these profiles.
1)Application server profile
2)Deployment manager profile
3)Custom profile
4)Cell profile
5)Administrative agent profile
6)Job manager profile
Application server profile : The application server profile defines a single standalone application server . The profile consists of one cell, one node, and one server
The server has a dedicated administrative console.
Deployment manager profile : The deployment manager profile defines a deployment manager in a distributed server environment. Although you can conceivably have the Network Deployment package and run only standalone servers
A cell for the administrative domain
A node for the deployment manager
A deployment manager with an administrative console
No application servers
WebSphere Application Server V7: Working with Profiles on Distributed Systems
After you have the deployment manager, you can:
Federate nodes built either from existing application server profiles or custom profiles.
Create new application servers and clusters on the nodes from the administrative console.
Custom profile : A custom profile is an empty node, intended for federation to a deployment manager. This type of profile is used when you build a distributed server environment. You use a custom profile for these purposes:
1. Create a deployment manager profile.
2. Create one custom profile on each node on which you will run application servers.
3. Federate each custom profile to the deployment manager, either during the custom profile creation process or later by using the addNode command.
4. Create new application servers and clusters on the nodes from the administrative console.
Cell profile :
Cell profile is actually a combination of two profiles: a deployment manager profile and an application server profile. The application server profile is federated to the cell. The deployment manager and application server reside on the same system. This type of profile lets you get a quick start with a distributed server environment and is especially useful for test environments that typically have all nodes on one test system.
Administrative agent profile:
An administrative agent profile is created on the same node as the standalone servers and can only manage nodes on that server. The node configuration for each standalone server is totally separate from any other servers on the system, but it can be managed using the administrative console on the administrative agent.
Job manager profile(New in V7):
The job manager is a new server type that was added to support flexible management. A job manager is defined by a job manager profile.
To participate in flexible management, a standalone application server first registers itself with the administrative agent. The administrative agent must then register the node for the application server with the job manager. If a deployment manager wants to participate in an environment controlled by a job manager, the deployment manager registers directly with the job manager; no administrative agent is involved in this case.
The main use of the job manager is to queue jobs to application servers in a flexible management environment. These queued jobs are pulled from the job manager by the administrative agent and distributed to the appropriate application server or servers.