WebSphere Extended Deployment V6.0.x     操作系统: AIX, HP-UX, Linux, Solaris, Windows

xd_hadmgrAdd command

The xd_hadmgrAdd command incorporates a new deployment manager profile into a cell. The new deployment manager profile is converted into an 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.

Syntax

[distributed platforms] The command syntax is as follows:
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 are required when creating the first standby deployment manager only.

Parameters

The following options are available for the xd_hadmgrAdd command:

-hostname <host name>
Specifies the host name used to connect to the existing deployment manager.
-port <port>
Specifies the port 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 proxy server's JMX SOAP address.
-proxyServerHttpPort <port> <secure_port>
Specifies the proxy server's HTTP ports.
-user <user>
Specifies the user name used to connect to the existing deployment manager.
-password <password>
Specifies the password used to connect to the existing deployment manager.
-quiet
Suppresses the progress information that the xd_hadmgrAdd command prints in normal mode.
-logfile <filename>
Specifies the location of the log file to which information gets written. By default, the log file is called hadmgrAdd.log and is created in the logs directory of the profile for the node being added.
-replacelog
Replaces the log file instead of appending to the current log. By default, the xd_hadmgrAdd command appends to the existing trace file. This option causes the xd_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 is not necessary if unique ports were assigned to the deployment manager profile when it was created.
-help
Displays syntax help.

Usage

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 –uniquePort when you run the xd_hadmgrAdd command, as shown below 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.

After creating the profile you have:
Description Name
WebSphere Application Server home directory /WebSphere/AppServer/
Existing deployment manager profile /shared/profiles/PrimaryManagerNode
New deployment manager profile /shared/profiles/StandbyManagerNode
Run the xd_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:
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

Using xd_hadmgrAdd makes the following changes to your cell configuration:

  1. 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.
  2. 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.
  3. The on demand router (ODR) is configured with the following:
    1. wc_admin and ws_admin_secure HTTP transport channels.
    2. JMX_SOAP_PROXY_ADDRESS endpoint.
  4. The deployment managers are reconfigured as follows:
    1. Their JMX_SOAP_CONNECTOR addresses point to the ODR’s JMX_SOAP_PROXY_ADDRESS.
    2. They have a JMX_SOAP_PROXY_ADDRESS added that holds the same configured host or port as their original JMX_SOAP_ADDRESS.

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:


ODR configuration with a non-highly-available deployment manager

To eliminate the ODR as a single point of failure, a HA ODR configuration is recommended with at least two ODRs receiving traffic from an internet protocol spraying device. In this case, the deployment managers JMX_SOAP_ADDRESS configured host name points to the device:


Internet protocol sprayer

The HA deployment manager function only supports use of the JMX SOAP connector. The JMX RMI connector is not supported in this configuration.




相關概念
The high availability deployment manager
相關工作
Configuring a high availability deployment manager environment
相關參考
参考主题    

使用条款 | 反馈

最近更新日期: Aug 14, 2006 2:00:44 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/odoe_task/rxd_hadmgrAdd.html

© Copyright IBM Corp. 2005, 2006. All Rights Reserved.
本信息中心基于 Eclipse 技术。(http://www.eclipse.org)