Configure deployment managers for a single, central point of administrative control for all elements in a WebSphere® Application Server distributed cell.
If you plan to change the system clock, stop all the
application servers, the node agent servers, the deployment manager
server, the administrative agent server, and the job manager server
first. After you stop the servers, change the system clock, and then
restart the servers. If you change the system clock on one system,
you must ensure the clocks on all systems that communicate with each
other and have WebSphere Application Server installed
are synchronized. Otherwise, you might experience errors, such as
security tokens no longer being valid.
Deployment managers are administrative agents that provide a centralized management view for all nodes in a cell, as well as management of clusters and workload balancing of application servers across one or several nodes in some editions. Each cell contains one deployment manager.
A deployment manager hosts the administrative console.
When you create a deployment manager profile, a deployment manager is created. You can run the deployment manager with its default settings. However, you can change the deployment manager configuration settings, such as the ports that the process uses, custom services, logging and tracing settings, and so on. To view information about managing a deployment manager, use the settings page for a deployment manager.
You configured a deployment manager with options that you selected.
You can continue to administer your product by doing such tasks as configuring cells and managing nodes, node agents, and node groups.
You can use the deployment manager Diagnostic Provider to test connectivity between the deployment manager and the node agents. Click
from the navigation of the administrative console. After running the diagnostic provider, click on the message text to get to the detail page that shows the node agent status. If the value field of the node agent is j2ee.state.stopped, the value usually means that the node agent is stopped. However, it can also mean that the deployment manager has lost network connectivity with the node agent. The deployment manager cannot distinguish between these two cases.