Network Deployment (Distributed operating systems), v8.0 > Set up the application serving environment > Administer nodes and resources > Work with dmgrs - centralized cell management
Configure dmgrs
Configure dmgrs for a single, central point of administrative control for all elements in a WAS distributed cell.
If you plan to change the system clock, stop all the application servers, the node agent servers, the dmgr server, the admin 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, ensure the clocks on all systems that communicate with each other and have WAS installed are synchronized. Otherwise, you might experience errors, such as security tokens no longer being valid.
Deployment managers are admin 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 dmgr.
A dmgr hosts the administrative console.
When you create a dmgr profile, a dmgr is created. We can run the dmgr with its default settings. However, you can change the dmgr 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 dmgr, use the settings page for a dmgr.
Procedure
- Click System administration > Deployment manager from the navigation tree of the administrative console to access the settings page for a dmgr.
- Configure the dmgr by clicking a property, such as Custom services, and specifying settings.
- Optionally register or unregister the dmgr with the job manager.
A job manager allows you to submit administrative jobs asynchronously for dmgrs and for application servers registered to admin agents. Click System administration > Deployment manager. Under Additional Properties, click Job managers > Register/unregister with job manager.
Results
You configured a dmgr with options that you selected.
What to do next
We can continue to administer your product by doing such tasks as configuring cells and managing nodes, node agents, and node groups.
We can use the dmgr Diagnostic Provider to test connectivity between the dmgr and the node agents. Click Troubleshooting > Diagnostic Provider > Tests > dmgr > DeploymentManagerDP > ping.-* 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 dmgr has lost network connectivity with the node agent. The dmgr cannot distinguish between these two cases.
Related
Deployment manager settings
Security considerations when in a multi-node WAS WAS ND environment