Valid for the File System connector: This description is true if you plan to use content connector to pick up files from a folder or from several folders. If you plan to connect content connector to a different kind of content source (e.g. Subversion), you may need a different setup – read on to find out.
The memoQ content connector connects two places:
- the folder where documents are added or updated, and
- the memoQ TMS that is supposed to pick them up, and manage their translation.
If you need to choose, place content connector close to the document source, and not to the memoQ TMS. In other words, install content connector on the computer where your source folder is stored, if possible.
If the source is in your organization, this is the preferred choice. Although you can connect content connector to a network folder, it requires extra setup (a special service account). But if the organization allows content connector to pick up documents from a local folder, you can set up the connections using the default access settings.
Using a remote file location? If the memoQ content connector is on a different computer than the one that has the source document folder, you can still set up the connection. Read on to find out how.
If the source is not in your organization – that is, it's not on a server that you control –, it's still a good idea to place the content connector on the same server where the files reside. There is a limitation: the memoQ content connector runs on Windows machines only, so the source server must also run Windows.
memoQ TMS always connects to content connector over the network, even when the content connector service and memoQ TMS are installed on the same machine. By default, content connector is listening on port 8080, using the HTTP protocol.
You can use a secure connection: To find out how, read the Secure the connection to content connector topic.
When you install content connector on a foreign machine, always arrange the connection to it – your customer must be ready to allow incoming connections to the content connector. content connector can be configured to use any port, but the communication will always be HTTP-style.
If the content source is not a regular file folder: If you plan to use content connector with Subversion or Git sources, content connector must be able to connect to the Subversion or Git server over the network. See the Configure content connector for SVN and Git connections topic.