The xd_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. The command must be run within the new deployment manager profile that is being added.
xd_hadmgrAdd -hostname (primary_dmgr_host) [-port (primary_dmgr_port)] -configRoot (fully_qualified_path_to_shared_configuration)] -workspaceRoot(fully_qualified_path_to_workspace) -proxyServerJmxSoapAddress (JMX_SOAP_host):(JMX_SOAP_host) -proxyServerHttpPort (HTTP_port)(HTTP_secure_port) [-uniquePort] [-user (uid)] [-password (pwd)] [-quiet] [-logfile (filename)] [-replacelog] [-trace] [-help]
The proxyServerJmxSoapAddress and proxyServerHttpPort parameters are required only when you are creating the first standby deployment manager.
The following options are available for the xd_hadmgrAdd command:
The following examples demonstrate correct syntax:
Starting with a pre-existing Network Deployment cell, installed and configured in the following directory structure:
Description | Name |
WebSphere Application Server home directory | /WebSphere/AppServer/ |
Existing deployment manager profile | /shared/profiles/PrimaryManagerNode |
where the /shared mountpoint is on a SAN FS device.
Run the profile configuration tool or wasprofile command line utility to create another deployment manager profile associated with this same Network Deployment installation. Create this profile on the shared disk, /shared mountpoint for this example. You must specify the correct host name for this deployment manager to listen on. You can specify the explicit port numbers for your standby deployment manager when you create the profile or you can specify the -uniquePort parameter when you run the xd_hadmgrAdd command, as shown in this example. You can specify any value for the cell name, because it is changed to match the cell name to which this HA deployment manager peer is added during the conversion process. You must specify a node name that is unique in the cell to which this HA deployment manager peer is added.
Description | Name |
WebSphere Application Server home directory | /WebSphere/AppServer/ |
Existing deployment manager profile | /shared/profiles/PrimaryManagerNode |
New deployment manager profile | /shared/profiles/StandbyManagerNode |
xd_hadmgrAdd.bat.sh –hostname a.a.a.a -port 8880 -configRoot /shared/profiles/PrimaryManagerNode/config -workspaceRoot /shared/profiles/PrimaryManagerNode -proxyServerJmxSoapAddress x.x.x.x:8880 -proxyServerHttpPort 9060 9043 -user wsadmin -password ******** -uniquePort
If you install the centralized installation manager repository, and after you create the second deployment manager profile, change the value of the CENTRALIZED_INSTALL_REPOSITORY_ROOT property in the install_root\properties\cimgr.props file from c:\ProgramFiles\IBM\WebSphere\AppServer\repository_folder to ${WAS_INSTALL_ROOT}/repository_folder.
Using the xd_hadmgrAdd command makes the following changes to your cell configuration:
Using the xd_hadmgrAdd command makes the following changes to your cell configuration:
As a result of the configuration change, the ODR hosts the logical endpoints for the deployment manager and proxies communication requests for the deployment manager to the active deployment manager.
For example in a non-HA ODR configuration, the deployment manager configured host name points to the ODR:
To eliminate the ODR as a single point of failure, a HA ODR configuration is recommended with at least two on demand routers receiving traffic from an internet protocol spraying device. In this case, the deployment managers JMX_SOAP_ADDRESS configured host name points to the device:
The HA deployment manager function only supports use of the JMX SOAP connector. The JMX RMI connector is not supported in this configuration.