memoQ system architecture and ports

Entity Connection protocol
memoQweb (client) HTTP(S)
content connector client HTTPS
content connector Subversion SVN’s custom protocol
content connector file system Standard file system access (smb)
memoQweb private API WCF (TCP / Secure TCP / HTTPS)
preview SDK

Named pipe/REST (HTTP)

Only local calls are accepted. No calls from remote machines.
websearch HTTP(S)
XSLT preview HTTP(S)
content connector HTTP(S)
HTTPS/secure TCP HTTPS/secure TCP
memoQweb private API WCF (TCP/Secure TCP/HTTPS)
memoQ private API WCF (TCP/Secure TCP/HTTPS)
email notification SMTP (over SSL)
error reporting HTTPS
activation Custom protocol over HTTP (with RSA public/private encryption used in inner protocol)
Active Directory AD /LDAP
database Configurable as one of the standard MS SQL Remote access protocols (shared memory/TCP/IP/named pipe, TLS)
file store Standard File System Access (SMB)
custom code execution WCF (named pipe)
custom code execution Standard Local Application Call
TM plugins HTTP(S), depending on the plugin
TB plugins HTTP(S), depending on the plugin
MT plugins HTTP(S), depending on the plugin
telemetry HTTPS
memoQ update HTTPS
webservices API (SOAP) HTTP(S)
resources API (REST) HTTP(S)
CMS API (REST) HTTP(S)
WordPress connector Out of memoQ control
memoQweb SSO HTTPS
memoQ server SSO HTTPS
IDP’s integrations HTTPS
content connector Git HTTPS
hey memoQ WSS (WebSocket Secure)
business analytics API HTTP(S)
memoQ AGT (private) API HTTPS
Open Al API HTTP

memoQ uses:

  • TCP Port 80

  • TCP Port 443

  • TCP Port 8086

  • TCP Port 2705 (Soon to be removed)