Server-to-server workflows

memoQ TMSs can talk to each other. Here is an example setup:

  • Company A is an enterprise who want some of their content translated. They have a memoQ TMS, Server A - it is the parent server in this example.
  • Company B is a translation agency who provides translation for Company A. They also have a memoQ TMS, Server B - it is the child server in this example.

  • Translator is a person who works as a translator for Company B. Translator has memoQ translator pro, and connects to the memoQ TMS of Company B.

    Note: To make the description simpler, we do not mention reviewers. Where you see "Translator", think "Translator, Reviewer 1 or Reviewer 2".

If a connection is set up between the two servers, Translator can connect to Server B, and get suggestions from translation memories and term bases on Server A. This is really useful for Company A, who can do this in a very secure way: by opening a single port on their firewall for Company B. Translator does not connect to Server A at all. Their work goes into a translation memory on Server B.

To set up the connection:

  1. To ensure secure communication, system administrator of the parent server buys and installs a certificate. It cannot be self-signed, because that is not compatible with HTTPS connections. If Company A already has a certificate from a certification authority for the parent server's domain, they can use it and do not need to buy a new one.
  2. They also turn on at least one secure protocol (Secure TCP or HTTPS) on the parent server, using memoQ TMS deployment tool.
  3. To authenticate on the parent server, the child server also needs a certificate. It can be self-signed - translation companies do not need to buy one. If the child server is in the cloud, you need to ask memoQ support to create the certificate. If the child server is not in a cloud, the system administrator installs the certificate, and chooses it in memoQ TMS deployment tool.
  4. The child server's memoQ TMS administrator exports the public key of the certificate using the Server Administrator window's Server connections tab. Then they send the exported file to the parent server's administrator.
  5. If the parent server is not in a cloud, its system administrator adds the child certificate on the parent server using memoQ TMS deployment tool. If the parent server is in the cloud, you need to ask memoQ support to put the child certificate file into the appropriate folder.
  6. The parent server's memoQ TMS administrator creates a special user (a server connection) for the child server using the Server Administrator window's Server connections tab on the parent server. They also choose the child certificate in the Server connection properties window.
  7. If the parent project manager wants to give the child project manager direct access to the parent server, they give them the user name and password. If not, the child project manager can still open project packages coming from the parent server.

After this, Company A can create project packages for Company B, and send them to Company B - currently, they need to do this outside memoQ.

Company B imports the package on Server B, creating a fully configurable online project from it. They assign the work to Translator. Translator can use suggestions from translation memories and term bases on both Server A and Server B. Their work goes to Server B. When Translator finishes the job, the project manager at Company B can deliver it with a single click to Company A.

Warning: Due to the complexity of configuration, always test your server-to-server setup before using it for production purposes.