Configure deployment managers
Configure deployment managers 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 appservers, the node agent servers, and the deployment manager server first. Once 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 issues, such as security tokens no longer being valid.
Overview
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 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
Procedure
- Click System Administration > Deployment Manager from the navigation tree of the console to access the settings page for a deployment manager.
- Configure the deployment manager by clicking a property, such as Custom Services, and specifying settings.
Results
You configured a deployment manager with options that you selected.
What to do next
You can continue to administer your product by doing such tasks as configuring cells and managing nodes, node agents, and node groups
Running the deployment manager with a non-root user ID
Deployment manager settings
Related tasks
Considering security specific to a multi-node or process ND environment