Configuring deployment managers

Configure deployment managers for a single, central point of administrative control for all elements in a WebSphere Application Server distributed cell.

Before you begin

[AIX HP-UX Linux Solaris Windows] [iSeries] If you plan to change the system clock, stop all the application servers, 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, 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 issues, such as security tokens no longer being valid.

[z/OS] If you plan to change the system clock, stop all the application servers, the node agent servers, the deployment manager server, and the location service daemon first. Once you stop the servers and location service daemon, change the system clock, and then restart the servers and location service daemon. 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 issues, such as security tokens no longer being valid.

About this task

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.

[z/OS] WebSphere Application Server for z/OS uses workload management (WLM) as the primary vehicle for workload balancing.

A deployment manager hosts the administrative console.

.

[z/OS] The Java virtual machine (JVM) for the deployment manager runs in 31-bit mode by default. The maximum amount of virtual memory available to each JVM on the z/OS operating system in 31-bit mode is 2 gigabytes (GB). However, because of product requirements, the amount of virtual memory that is available to each JVM is somewhat less. To obtain more virtual memory for the deployment manager server, or any other server, run the server in 64-bit mode. If you have applications that require large amounts of virtual memory, the applications might need to run on servers configured for 64-bit mode.

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

  1. Click System Administration > Deployment Manager from the navigation tree of the administrative console to access the settings page for a deployment manager.
  2. Configure the deployment manager by clicking a property, such as Custom Services, and specifying settings.
  3. [z/OS] If you specify the server short name as eight characters, follow the directions to convert the default seven-character short name to eight characters.

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



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Feb 19, 2011 5:25:36 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v610web&product=was-nd-mp&topic=trun_watch_cellmgr
File name: tagt_watch_cellmgr.html