![[AIX Solaris HP-UX Linux Windows]](../images/ngdist.svg)
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.
Run the hadmgrAdd command within the new deployment manager profile that is being added. The HA deployment manager function supports use of the JMX SOAP connector only. The JMX RMI connector is not supported in this configuration.
Usage
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_port
-proxyServerHttpPort HTTP_portHTTP_secure_port
[-uniquePort] [-user user_name] [-password password]
[-quiet] [-logfile file_name] [-replacelog] [-trace] [-help]The proxyServerJmxSoapAddress and proxyServerHttpPort parameters are required only when you are creating the first standby deployment manager.
Parameters
The following options are available for the hadmgrAdd command:
- -hostname <host name>
- Specifies the host name that is used to connect to the existing deployment manager.
- -port <port>
- Specifies the default SOAP port that is used to connect to the existing deployment manager.
- -configRoot <fully qualified path>
- Specifies the fully-qualified configuration path.
- -workspaceRoot <fully qualified path>
- Specifies the fully-qualified workspace path.
- -proxyServerJmxSoapAddress <host:port>
-
Specifies the host name or IP address of the On Demand Router (ODR) and a port for the ODR. This port must be an unused port for running the
wsadminscripts. - -proxyServerHttpPort <port> <secure_port>
- Specifies the HTTP ports for the proxy server. Select two free ports on the ODR and IP sprayer host. These ports must be used to access the administrative console by way of the ODR.
- -user <user name>
- Specifies the user name that is used to connect to the existing deployment manager.
- -password <password>
- Specifies the password that is used to connect to the existing deployment manager.
- -quiet
- Suppresses the progress information that the hadmgrAdd command prints in normal mode.
- -logfile <filename>
- Specifies the location of the log file to which information gets
written. By default, the hadmgrAdd.log file is
created in the
logsdirectory of the profile for the node that is being added. - -replacelog
- Replaces the log file instead of appending to the current log. By default, the hadmgrAdd command appends to the existing trace file. This option causes the hadmgrAdd command to overwrite the trace file.
- -trace
- Generates additional trace information in the log file for debugging purposes.
- -uniquePort
- Checks for port conflict. If the new port is conflict with the existing ports, the new port increments by one until a free port is found. This process is not necessary if unique ports were assigned to the deployment manager profile when it was created.
- -help
- Displays syntax help.
Example
- Start with an existing WebSphere Application
Server Network Deployment cell
that is installed and configured with the following directory structure:
- WebSphere Application Server home directory: app_server_root
- Existing deployment manager profile: /shared/profiles/PrimaryManagerNode
- Run the Profile Management Tool plug-in or the wasprofile command
line utility to create another deployment manager profile associated
with this same Network Deployment installation. Create the 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 hadmgrAdd command, as shown in this example. You can specify any value for the cell name. During the conversion process the cell name value is changed to match the cell name to which the HA deployment manager peer is added. You must specify a node name that is unique in the cell to which this HA deployment manager peer is added.
You have the following directory structure after you create the profile:- WebSphere Application Server home directory: app_server_root
- Existing deployment manager profile: /shared/profiles/PrimaryManagerNode
- New deployment manager profile: /shared/profiles/StandbyManagerNode
- Run the hadmgrAdd command to convert the new deployment manager profile into
an HA deployment manager peer in the same cell in which the existing deployment manager profile
exists.
hadmgrAdd.sh|bat -hostname a.a.a.a -port 8879 -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 app_server_root\properties\cimgr.props file
from c:\ProgramFiles\IBM\WebSphere\AppServer\repository_folder to ${app_server_root}/repository_folder.
- The new deployment manager is configured to use the same configuration repository instance as the existing deployment manager, which must be on a shared device with the existing deployment manager.
- The new deployment manager is configured to use the same specified workspace shared directory, which must be on a device shared with the existing deployment manager.
- The ODR is configured with the WC_adminhost and WC_adminhost_secure HTTP transport channels and the JMX_SOAP_PROXY_ADDRESS endpoint.
- The JMX_SOAP_CONNECTOR addresses of the deployment managers point to the JMX_SOAP_PROXY_ADDRESS of the ODR.
- The deployment managers have an added JMX_SOAP_PROXY_ADDRESS that holds the same configured host or port as their original JMX_SOAP_ADDRESS.
