Based on this knowledge a small REST-service will be developed, which is able to deliver a TBX-file for a certain language combination of a certain termBase. The reason for this service is to be able to separate the Multiterm installation from the translate5 installation. This way both can run on different machines.

The REST-service supports 2 methods:

1. get list of available termbases
2. get TBX-file of a termbase for a specific language combination
   • language combination and identifier of the termBase are passed to this REST-service, the TBX-file is returned.

• the REST-service connects to Multiterm via COM
• the REST-service will be build with phpdaemon

• Multiterm API is not able to directly export a TBX file. The easiest way to get the terms of a termbase is by walking through the entries of a termbase and save each term to translate5 database. Afterwards the termTagging can be triggered.

• A remote termbase can only be connected by another Multiterm instance. Therefore
  • either the REST-service for Multiterm can be directly installed on the server, where the needed termbase is located
  • or on another machine (if needed located in another LAN) it is necessary to install a local Multiterm instance. This Multiterm in turn connects to the remote Multiterm instance and queries the remote termbase