Install Multiple Replicators

For example, to create two services, one that reads from MySQL and another that writes to MongoDB on the same host:

1. Install the Tungsten Replicator package or download the Tungsten Replicator tarball, and unpack it:

   shell> cd /opt/continuent/software
   shell> tar zxf tungsten-replicator-8.0.4-132.tar.gz

2. Create the proper directories with appropriate ownership and permissions:

   shell> sudo mkdir /opt/applier /opt/extractor
   shell> sudo chown tungsten: /opt/applier/ /opt/extractor/
   shell> sudo chmod 700 /opt/applier/ /opt/extractor/

3. Change to the Tungsten Replicator directory:

   shell> cd tungsten-replicator-8.0.4-132

4. Using the below example, create the /etc/tungsten/extractor.ini to configure the extractor reading from MySQL:

   Example extractor.ini

   [defaults]
   install-directory=/opt/extractor
   user=tungsten
   profile-script=~/.bash_profile
   mysql-allow-intensive-checks=true
   disable-security-controls=true
   executable-prefix=ext
   rest-api-admin-user=apiuser
   rest-api-admin-password=secret
   replicator-rest-api-address=0.0.0.0
   
   [alpha]
   master=offboardhost
   members=offboardhost
   enable-heterogeneous-service=true
   replication-port=3306
   replication-user=tungsten_alpha
   replication-password=secret
   datasource-mysql-conf=/etc/my.cnf
   svc-extractor-filters=colnames,pkey
   property=replicator.filter.pkey.addColumnsToDeletes=true
   property=replicator.filter.pkey.addPkeyToInserts=true
   mysql-enable-enumtostring=true
   mysql-enable-settostring=true
   mysql-use-bytes-for-string=false

   Show argument definitions

   ▸install-directory=/opt/extractorInstallation directory.

   user=tungstenOS System User, for example tungsten. DO NOT use root.

   profile-script=~/.bash_profileAppend commands to include env.sh in this profile script.

   ▸mysql-allow-intensive-checks=trueFor MySQL installation, enables detailed checks on the supported data types within the MySQL database to confirm compatibility.

   ▸disable-security-controls=trueDisables all forms of security, including SSL, TLS and authentication.

   ▸executable-prefix=extAdds a prefix to command aliases.

   rest-api-admin-user=apiuserSpecify the initial Admin Username for API access.Available from v7.0.0

   rest-api-admin-password=secretSpecify the initial Admin User Password for API access. rest-api-admin-password alias only available from version 7.1.2 onwards.Available from v7.0.0

   replicator-rest-api-address=0.0.0.0Address for the API to bind too.Available from v7.0.0

   This is a standard configuration using the default ports, with the directory /opt/extractor.

5. Using the below example, create the /etc/tungsten/applier.ini to configure the applier for writing to MongoDB:

   Example applier.ini

   [defaults]
   install-directory=/opt/applier
   profile-script=~/.bash_profile
   skip-validation-check=InstallerMasterSlaveCheck
   executable-prefix=app
   rest-api-admin-user=apiuser
   rest-api-admin-password=secret
   replicator-rest-api-address=0.0.0.0
   
   [alpha]
   master=localhost
   members=localhost
   role=slave
   datasource-type=mongodb
   replication-user=tungsten
   replication-password=secret
   rmi-port=10002
   master-thl-port=2112
   master-thl-host=localhost
   thl-port=2113

   Show argument definitions

   ▸install-directory=/opt/applierInstallation directory.

   profile-script=~/.bash_profileAppend commands to include env.sh in this profile script.

   ▸skip-validation-check=InstallerMasterSlaveCheckDo not run the specified validation check.

   ▸executable-prefix=appAdds a prefix to command aliases.

   rest-api-admin-user=apiuserSpecify the initial Admin Username for API access.Available from v7.0.0

   rest-api-admin-password=secretSpecify the initial Admin User Password for API access. rest-api-admin-password alias only available from version 7.1.2 onwards.Available from v7.0.0

   replicator-rest-api-address=0.0.0.0Address for the API to bind too.Available from v7.0.0

   In this configuration, the Extractor THL port is specified explicitly, along with the THL port used by this replicator, the RMI port used for administration, and the installation directory /opt/applier.

6. Run tpm to install the software, once for each configuration file:

   shell> ./tools/tpm install --ini /etc/tungsten/extractor.ini
   shell> ./tools/tpm install --ini /etc/tungsten/applier.ini

   During the startup and installation, tpm will notify you of any problems that need to be fixed before the service can be correctly installed and started. If start-and-report is set and the service starts correctly, you should see the configuration and current status of the service.

7. Initialize your PATH and environment.

   shell> source /opt/extractor/share/env.sh
   shell> source /opt/applier/share/env.sh

8. You can now start and check the replication status, using the values of executable-prefix in front of the standard CLI tools to control the specific extractor or applier service

When multiple replicators have been installed, checking the replicator status through trepctl depends on the replicator executable location used. If /opt/extractor/tungsten/tungsten-replicator/bin/trepctl, the extractor service status will be reported. If /opt/applier/tungsten/tungsten-replicator/bin/trepctl is used, then the applier service status will be reported.

To make things easier, in the config examples above executable-prefix has been used, which will set up OS aliases. These aliases are setup when you source the relevant env.sh files, this will also happen by default when you login to the host providing profile-script has been specified.

The use of the prefix and aliases, then simplifies the use of all executables, for example, based on the setting of executable-prefix in the above config examples, to report the status of the extractor, you can execute:

shell> ext_trepctl status

Or to check the applier service:

shell> app_trepctl status

Alternatively, a specific replicator can be checked by explicitly specifying the RMI port of the service. For example, to check the extractor service:

shell> trepctl -port 10000 status

Or to check the applier service:

shell> trepctl -port 10002 status

When an explicit port has been specified in this way, the executable used is irrelevant. Any valid trepctl instance will work.

Further, either path may be used to get a summary view using multi_trepctl command:

shell> /opt/extractor/tungsten/tungsten-replicator/scripts/multi_trepctl
| host   | servicename | role   | state  | appliedlastseqno | appliedlatency |
| host1  | extractor   | master | ONLINE |                0 |          1.724 |
| host1  | applier     | slave  | ONLINE |                0 |          0.000 |