Installing the Translation Manager Service on multiple machines

Outscale the Translation ManagerService by installing it on a separate machine and configuring it to use the same Content Manager Database and Translation Manager Database.

Before you begin

Install the Translation Manager Service and Content Manager core on a supported Microsoft Windows operating systems. For more information, see Content Manager server and Topology Manager prerequisites.

Procedure

  1. Create the Content Manager Database using the appropriate PowerShell script.
  2. Create Translation Manager Database—run database scripts provided to create the Microsoft SQL Server or Oracle database where the Translation Manager stores Translation Jobs.
  3. On machine 1, perform a full installation of the Content Manager Server and including software modules you are using, including Translation Manager.
  4. On machine 2, install the following components (these are the minimum components required to run the Translation Manager Service):
    • Content Manager core
    • Translation Manager Service—run the installer and install the Translation Manager Service (deselect other Components)
    • External Content Library—and dependent modules (if you are using ECL and want to send ECL items for translation)
  5. On machines 1 and 2, open the TranslationManager.xml configuration file, by default located in your Tridion installation \config directory, and set the following configuration options:
    • SmtpServer—the location and connection details of the SMTP server which is used to send notification e-mails
    • TcmPollingInterval the frequency with which the Translation Manager is polled for Translation Jobs waiting transferal to the translation management system.
    • TmsPollingInterval the frequency with which the translation management system is polled to see whether Translation Jobs have been completed.
  6. On machine 1, open the TranslationManager.xml configuration file, by default located in your Tridion installation \config directory, and set the various configuration options—for more information, see the Translation Manager documentation on the implementor's documentation portal.
  7. Save and close the TranslationManager.xml configuration file.
  8. Restart the Translation Manager Service to ensure your changes are enforced.