Deployment Sources
The following primary deployment sources are available:
Tar/GZip packages: Using the TAR/GZip package creates a local directory that enables you to perform installs and updates from the extracted 'staging' directory.
RPM Packages: Using the RPM package format is more suited to using the INI file format, as hosts can be installed and upgraded to the latest RPM package independently of each other.
All packages are named according to the product, version number, build release and extension. For example:
tungsten-replicator-8.0.4-132.tar.gz
The version number is 8.0.4 and build number 132. Build numbers indicate which build a particular release version is based on, and may be useful when installing patches provided by support.
Using the TAR/GZipped files
To use the TAR/GZipped packages, download the files to your machine and unpack them:
shell> cd /opt/continuent/software
shell> tar zxf tungsten-replicator-8.0.4-132.tar.gz
This will create a directory matching the downloaded package name, version, and build number from which you can perform an install. To use, you will need to use the tpm command within
the tools directory of the extracted package:
shell> cd /opt/continuent/software/tungsten-replicator-8.0.4-132
shell> tools/tpm install
Using the RPM package files
Installation
Installing the RPM package will do the following:
- Create the
tungstensystem user if it doesn't exist. - Make the
tungstensystem user part of themysqlgroup if it exists. - Create the
/opt/continuent/softwaredirectory. - Unpack the software into
/opt/continuent/software - Define the
$CONTINUENT_PROFILESand$REPLICATOR_PROFILESenvironment variables - Update the profile script to include the
/opt/continuent/share/env.shscript - Create the
/etc/tungstendirectory if it doesn't exist - Run
tpm installif the/etc/tungsten/tungsten.inifile exists.
If no /etc/tungsten/tungsten.ini was found, then after creation you will need to manually install the software, using the following steps as an example:
shell> cd /opt/continuent/software/tungsten-replicator-8.0.4-132
shell> tools/tpm install
Although the RPM packages complete a number of the prerequisite steps required to configure your cluster, there are additional steps, such as configuring ssh, that you still need to complete.
For more information, see "Installation Prerequisites".
By using the package files you are able to set up a new server by creating the /etc/tungsten/tungsten.ini file and then installing the package. Any output from the tpm command will go
to /opt/continuent/service_logs/rpm.output.
If you download the package files directly, you may need to add the signing key to your environment before the package will load properly.
For yum platforms (RHEL/CentOS/Amazon Linux), the rpm command is used:
root-shell> rpm --import http://www.continuent.com/RPM-GPG-KEY-continuent
For Ubuntu/Debian platforms, the gpg command is used:
root-shell> gpg --keyserver keyserver.ubuntu.com --recv-key 7206c924
Upgrades
If you upgrade to a new version of the RPM package it will do the following:
- Unpack the software into
/opt/continuent/software - Run
tools/tpm update --replace-releaseif the/etc/tungsten/tungsten.inifile exists.
The tpm update will restart all Continuent Tungsten services so you do not need to do anything after upgrading the package file.