Common Reference

Converting from Staging to INI

If you currently use the Staging installation method and wish to convert to using INI files, use the following procedure.

You can also try using the script in "Using the translatetoini.pl Script"

If running Tungsten Clustering, place cluster(s) in MAINTENANCE Mode:
```
shell> cctrl
cctrl> set policy maintenance
```
Create the text file /etc/tungsten/tungsten.ini on each node. They should all be the same, therefore it is advised to create the file on one host and then copy it to all other hosts.
```
shell> sudo mkdir /etc/tungsten
shell> sudo chown -R tungsten: /etc/tungsten
shell> chmod 700 /etc/tungsten
shell> touch /etc/tungsten/tungsten.ini
shell> chmod 600 /etc/tungsten/tungsten.ini
```
Each section in the INI file replaces a single tpm configure call. The section name inside of [square brackets] is used as the service name. In the case of the [defaults] section, this will act like the tpm configure defaults command. The property names in the INI file are the same as what is used on the command line. Simply remove the leading -- characters and add it to the proper section.
For example, to seed the /etc/tungsten/tungsten.ini file, use the output of tpm reverse:
```
shell> tpm reverse > /etc/tungsten/tungsten.ini
```
Edit the new ini file and clean it up as per the rules above. For example, using vi:
```
shell> vi /etc/tungsten/tungsten.ini
:%s/tools\/^tpm configure /[/g
:%s/^--//g
:%s/\s*\\$//g
```
Important
In the above example, you MUST manually add the trailing square bracket ] to the end of the defaults tag and to the end of every service name section. Just search for the opening square bracket [ and make sure there is a matching closing square bracket for every one.
On every node, extract the software into /opt/continuent/software/[extracted_dir]
Warning
Make sure you have the same release that is currently installed.
```
shell> cd /opt/continuent/software
shell> tar zxf tungsten-clustering-8.0.4-132.tar.gz
```
For Clustering Users
If this is an Multi-Site/Active-Active topology, make sure you extract both the clustering and replication packages.
On each node, change to the extracted directory and execute the tpm command:
For Clustering Users
Execute this step on the replicas first, then switch the primary - this procedure will restart the Tungsten services so switching your primary will avoid interruption of service.
```
shell> cd /opt/continuent/software/tungsten-clustering-8.0.4-132.tar.gz
shell> ./tools/tpm update --replace-release
```
This will read the tungsten.ini file and apply the settings. The tpm command will identify what services likely need to be restarted and will just restart those. You can manually restart the desired services if you are unsure if the new configuration has been applied.
For Clustering Users
The tpm update command may cause a brief outage while restarting the connectors. This will occur if you are upgrading to a new version You can avoid that with:
shell> ./tools/tpm update --replace-release --no-connectors
Afterwards, the connectors must still be restarted on each server to pick up the new version or any changes, this can be done when convenient, by running:
shell> tpm promote-connector
If you have a Tungsten Clustering Multi-Site/Active-Active topology, you must also update the cross-site replicators:
- On each node, change to the extracted replicator directory and execute the tpm command:
```
shell> cd /opt/continuent/software/tungsten-replicator-8.0.4-132
shell> ./tools/tpm update --replace-release
```
- Once all steps have been completed and the cluster(s) are stable, take each cluster out of MAINTENANCE mode by setting the policy back to AUTOMATIC:
```
shell> cctrl
cctrl> set policy automatic
```

Using the `translatetoini.pl` Script

You can download a script from the documentation library, ⬇ translatetoini.pl.

You must have Perl installed to be able to execute the script.

To use the script, you can either run the script and paste in the staging output, or pipe the output from tpm reverse directly into the script. When supplying the staging output, you should supply the output from within the configured staging directory. For example:

shell> ./tools/tpm reverse|../translatetoini.pl

The script will create the file tungsten.ini in the current directory containing the converted output.

To change the destination, use the --filename option:

shell> ./tools/tpm reverse|../translatetoini.pl --filename=t.ini

You can also combine multiple staging configurations into a single INI conversion by appending to an existing INI file by adding the --append option:

shell> ./tools/tpm reverse|../translatetoini.pl --append

You should always check the INI file before using it for a live installation to ensure that all of the options and parameters have been identified and configured properly.

A training video is available on how to perform the staging to INI file conversion using the translatetoini.pl script:

Click here for a video of the INI conversion procedure, showing the full process from start to finish.

Using the translatetoini.pl Script​

Using the `translatetoini.pl` Script