Your Semaphore installation

Linux “services”

The following applications continuously run on the Semaphore server (if installed):

• Classification Server (semaphore-cs) - “ClassificationServer” process(es), one for each configured thread plus a controller process.
• Studio (semaphore-studio) - The master Semaphore Studio application that provides access to the “Knowledge Model Management”, “Document Analyzer” and “SES API” (Widgets) sub-components via the TCP/IP ports these separate sub-components listen on. This runs as a web application in a built-in Apache Tomcat instance (which runs within a Java VM).
• Knowledge Model Management (semaphore-kmm) - The model update sub-component of Semaphore Studio. This runs as a web application in a built-in Apache Tomcat instance (which runs within a Java VM).
• Document Analyzer (semaphore-da) - This “document analyzer” sub-component of Semaphore Studio. This runs as a web application in a built-in Apache Tomcat instance (which runs within a Java VM).
• Semantic Enhancement Server (semaphore-ses) - A java process that utilizes a built-in Solr back-end.
• Reconciliation Server (semaphore-rs) - the backend to any mapping services - such as from KMM or from the OpenRefine application
• Precision and Recall server (semaphore-pr) - a web service to enable regression analysis of classification quality.

The standard Semaphore installation creates the relevant “systemd” scripts for Semaphore software which are set to automatically start the services on reboot. The “semaphore” systemd script can be used to control all studio components, for example “systemctl start semaphore” will start the “semaphore-studio”, “semaphore-kmm”, and “semaphore-da” services.

Firewall considerations

There are a small number of TCP/IP ports used by Semaphore. By default, for the Semaphore server the following ports must be open externally:

• 5080 - Port for users to be able to access Semaphore Studio

The sub-components of Studio also listen on TCP/IP ports though they are generally not accessed across the network (and are installed as part of Semaphore Studio):

• 5081 - Default port for “Document Analyzer”, Semaphore Studio sub-component
• 5082 - Default port for “Knowledge Model Management”, Semaphore Studio sub-component
• 5083 - Default port for “Rulenet Manager”, Semaphore Studio sub-component
• 5084 - Default port for “SES Manager”, Semaphore Studio sub-component

There are additional ports used for components to talk to one another. If the applications are partitioned, that is, installed on different machines then these ports will also need to be open:

• 5058 - Classification Server integrations wishing to communicate with the Classification Server API (programmatically).
• 5059 - Classification Server administrators - it may be desirable to use this port for requests outside of business as usual requests. However, in many cases this is not required.
• 8983 - Semantic Enhancement Server clients (for example those applications wishing to access Semantic Enhancement Server functionality).

See Appendix - Detailed network firewall rules for further information.