To create the configuration use tpm to create the entire configuration with just one command. Before starting the installation, the prerequisites must have been completed (see Appendix B, Prerequisites). This takes the list of hosts, and a list of master services that will be configured, and then creates each service automatically:
On your staging server, download the release package.
Unpack the release package:
Change to the unpackaged directory:
Create the installation using the tpm:
./tools/tpm configure epsilon --topology=all-masters \ --install-directory=/opt/continuent \ --replication-user=tungsten \ --replication-password=password \ --master=host1,host2,host3 \ --members=host1,host2,host3 \ --master-services=alpha,beta,gamma \ --start-and-report=true
[epsilon] topology=all-masters install-directory=/opt/continuent replication-user=tungsten replication-password=password master=host1,host2,host3 members=host1,host2,host3 master-services=alpha,beta,gamma start-and-report=true
The description of each of the options is shown below; click the icon to hide this detail:
Click the icon to show a detailed description of each argument.
Replication topology for the dataservice Valid values are star,cluster-slave,master-slave,fan-in,clustered,cluster-alias,all-masters,direct
Path to the directory where the active deployment will be installed. The configured directory will contain the software, THL and relay log information unless configured otherwise.
For databases that required authentication, the username to use when connecting to the database using the corresponding connection method (native, JDBC, etc.).
The password to be used when connecting to the database using
The hostname of the master (extractor) within the current service. If the current host does not match this specification, then the deployment willby default be configured as a master/extractor.
Hostnames for the dataservice members
Data service names that should be used on each master
Start the services and report out the status after configuration
Host and service information is extracted in corresponding sequence as provided in the command-line options.
If the installation process fails, check the output of the
/tmp/tungsten-configure.log file for
more information about the root cause.
Once tpm has completed, the service will be started and the replication will be enabled between hosts.