Set dmgrs
Set dmgrs for a single, central point of administrative control for all elements in a WAS distributed cell.
If we plan to change the system clock, stop all the appservers, the node agent servers, the dmgr 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 we 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, we 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 appservers across one or several nodes in some editions. Each cell contains one dmgr.
A dmgr hosts the admin console.
When you create a dmgr profile, a dmgr is created. We can run the dmgr with its default settings. However, we can change the dmgr 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 deployment manager.
- Click System Administration > Deployment manager from the navigation tree of the admin console to access the settings page for a dmgr.
- Set 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 appservers registered to administrative 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.
Next steps
We can continue to administer the product by doing such tasks as configuring cells and managing nodes, node agents, and node groups.
You can use the dmgr Diagnostic Provider to test connectivity between the dmgr and the node agents. Click Trouble Shooting > Diagnostic Provider > Tests > dmgr > DeploymentMangaerDP > ping.-* from the navigation of the admin 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 tasks
Considering security specific to a multi-node or process ND environment