(Dist) Configure a high availability deployment manager environment
The high availability (HA) deployment manager function can be configured to eliminate single point of failure for administrative functions in a WebSphere Application Server Network Deployment cell.
(ZOS) This feature is supported only on distributed platforms and is not available on z/OS .
Privileges for the high availability (HA) deployment manager differ, depending on the various roles. Roles include monitor, operator, configurator, and administrator. If we are a user with either a monitor or a configurator role, we can only view the HA deployment manager information. If we have the role of operator or administrator, we have all the privileges for the HA deployment manager.
Before following these steps ensure the system environment has a suitable shared file system available, such as IBM SAN FS or NFS Version 4. To verify that the file system is suitable for use with the high availability deployment manager, use the file system locking protocol test for WAS. See the IBM File System Locking Protocol Test for WAS. The shared file system requirements are the same for both the failover of transaction logs and for the high availability deployment manager.
We must stop all deployment managers that are running in the environment before we can perform maintenance on the NFS drive. Use the extended repository service in conjunction with the HA deployment manager feature. In the event of a NFS failure, we can recover the latest configuration changes using the extended repository service.
If the deployment manager is also being used in the role of a job manager, the job manager functionality will not work after the deployment manager is converted to an HA configuration. A separate profile should be created for the job manager.
Each deployment manager must share the same master configuration repository and workspace area, which must be on the shared file system. Each deployment manager must also have read and write permissions to the shared master configuration repository and workspace area. The master configuration repository and workspace area default locations are install_root/profiles/deployment_manager/config and install_root/profiles/deployment_manager/wstemp/ directories.
File sharing is typically accomplished by installing the deployment manager on the shared file system. Sharing the entire installation is not mandatory, and an alternative is to locate only the deployment manager profiles on the shared file system. In the scenarios described in this topic, Intelligent Management is installed on the shared file system. For scenarios in which only the deployment manager configuration repository and workspace reside on the Network Attached Storage (NAS), read about thexd_hadmgrAdd command.
Set up a high availability deployment manager environment to eliminate the deployment manager as a single point of failure. When one deployment manager fails, a configured deployment manager can resume the work. See the high availability deployment manager.
Tasks
- Choose a topology. The HA deployment manager function can be configured in a variety of topologies. In a production environment, IBM recommends that each deployment manager runs on its own computer to increase availability. If a single on demand router (ODR) is in the topology, it must run on its own computer. To eliminate the ODR as a single point of failure, we can use multiple on demand routers in conjunction with an IP sprayer. A typical HA deployment manager environment requires at least three computers:
Computer name Processes A Deployment manager B Standby deployment manager C Node agent and on demand router - We can either create a new cell with an HA deployment manager configuration, or convert an existing cell to an HA deployment manager configuration.
To create a new cell with an HA deployment manager configuration:
- Install WAS on the shared file system.
- Install Intelligent Management on the shared file system.
- Create a deployment manager profile using the IP address for computer A.
- Start the deployment manager on computer A.
- Create a custom profile using the IP address for computer C. Federate computer C with the deployment manager.
- Create an ODR on the federated custom profile.
- Create a deployment manager profile using the IP address for computer B.
- Run the xd_hadmgrAdd command within the deployment manager profile for computer B to convert it into a standby deployment manager. For more information, read about thexd_hadmgrAdd command.
To convert an existing cell to an HA deployment manager configuration:
- Install WAS on the shared file system.
- Install Intelligent Management on the shared file system.
- Create a deployment manager profile using the IP address for computer A and with the same cell and node name as the existing deployment manager.
- Use the backupConfig and restoreConfig command line utilities to relocate the existing cell configuration to the shared file system.
- Copy the tmsStorage folder and its contents from the existing deployment manager profile to the new deployment manager profile on the shared file system.
- Ensure that the existing cell configuration contains an ODR. Create an ODR if an ODR does not exist.
- Create a deployment manager profile using the IP address for computer B.
- Run the xd_hadmgrAdd command within the deployment manager profile for computer B to convert it into a standby deployment manager. For more information, read about thexd_hadmgrAdd command.
- Restart the deployment managers and on demand routers.
Multiple deployment managers are configured. The deployment manager is eliminated as a single point of failure because a primary deployment manager hosts the administrative function for the cell, and has backup deployment managers in standby node. If the primary deployment manager fails, the standby deployment managers can resume without losing work.
What to do next
After your high availability deployment manager environment is set up, we can manage the deployment managers in the administrative console. Click System administration > Deployment manager > All deployment managers to view and manage the configured deployment managers in the environment.
If we need to remove a high availability deployment manager from the cell, use the command line utility to remove the function. For more information about removing the high availability deployment manager from the cell, read about the xd_hadmgrRemove command.
Subtopics
- Add the signer certificate from the secondary deployment manager to the local trust store
To enable SSL in your high availability deployment manager environment, the local trust store must contain the signer certificate from the secondary deployment manager. If the trust store does not contain the signer certificate, add the certificate to the trust store to prevent errors and enable secure communication among the core group members.- The high availability deployment manager
The high availability (HA) deployment manager function is configured using a shared file system. When this configuration option is chosen, multiple deployment managers are configured. The benefit of the HA deployment manager function is that the deployment manager is no longer the single point of failure for cell administration. This is important in environments relying on automated operations, including application deployment and server monitoring.- Intelligent Management: hadmgrAdd command
The hadmgrAdd command incorporates a new deployment manager profile into a cell. The new deployment manager profile is converted to a highly available (HA) deployment manager peer in the same cell as the existing deployment manager profile.- Intelligent Management: hadmgrRemove command
Related:
The high availability deployment manager Add the signer certificate from the secondary deployment manager to the local trust store Configure rewriting rules Create and configure ODRs Intelligent Management: administrative roles and privileges Intelligent Management: hadmgrRemove command Intelligent Management: hadmgrAdd command IBM File System Locking Protocol Test for WAS