Verifies that the cluster exists.
Verifies that the cluster is standalone (an example of this is, that the cluster doesn't share its configuration with any other cluster).
Checks if a database with the same name as the cluster already exists. If so, an error is logged and the command performs the next task.
Creates an HA database with the same name as the cluster.
Creates the correct tables in the database.
Creates and/or modifies the appropriate resources in domain.xml.
This command is supported in remote mode only.
This option specifies the machine where the domain application server is located. The default is localhost.
The port number of the domain application server listening for administration requests. The default port number for Platform Edition is 4848. The default port number for Enterprise Edition is 4949.
This option specifies the user name associated with the administrative instance.
The ––password option is deprecated. Use ––passwordfile instead.
The file containing the domain application server password associated with the administrative instance. The password is defined in the following form: AS_ADMIN_PASSWORD=password. Where password is the actual administrator password for the domain.
Indicates that any output data must be very concise, typically avoiding human-friendly sentences and favoring well-formatted data for consumption by a script. Default is false.
Setting to true will echo the command line statement on to the standard output. Default is false.
If set to true (default), only the required options are prompted.
If set to true, uses SSL/TLS to communicate with the domain administration server.
This is the device size in MegaBytes (MB). The valid range is between 208MB and 8+ gigabytes (GB).
This is the number of the HA agent port. The default is 1862.
The file containing the high-availability password associated with the administrative instance. The password is defined in the following form: HADBM_ADMINPASSWORD=password, HADBM_DBPASSWORD=password, HADBM_SYSTEMPASSWORD=password. Where password is the actual HA administrator password for the domain.
A fresh installation of the high-availability does not have a domain nor its packagepath registered. This can cause problems when you wish to use HADB on a remote machine in certain cases. If the remote machine's HADB root directory does not have exactly the same directory structure as the client machine's, then the registration of the remote machine will fail. There are 3 ways to handle this situation:
Register the packagepath and domain manually on the remote machine with hadbm.
Run the following commands locally on the remote machine to bootstrap it:
configure-ha-cluster ––devicesize 208 ––hosts hostname,hostname c1
Use the––packagepath option. to identify the HADB-root path on the remote machine. This is the path you would use if you were logged on to the remote machine.
This is a list of comma separated host names where the HADB instance is configured. The number of hosts must be greater than 1 and must be an even number. The same host names can be repeated. Use fully qualified hostnames when specifying the hostlist interfaces explicitly for hosts with multiple network interfaces.
This is a list of property name/value pairs, which are separated by a colon.
To explicitly specify a portbase number for HADBM nodes, use the ––property portbase=base_number option.
This is a basic example of how the cammand is used.
asadmin>configure-ha-cluster --user admin --passwordfile passwordfile --hosts red.iplanet.com.host1,red.iplanet.com.host2 cluster1 The command configuration-ha-cluster has executed successfully.