Arclink Server Setup
The Arclink server to work correctly need to have access to Inventory, Routing and data from an SDS structure. With the correct setup the arclink server can help users to obtain time window waveforms in miniSeed or fullSeed format, dataless seed volumes, or even Inventory or Routing information in XML formats. The Arclink server implementation is divided in two parts, one the server, written in C++ and the request handler (written in python).
The Arclink server doesn't know anything about seiscomp, databases, and data types. It just open a network port and keep listening for incoming connection. When it receives a request, the server start a request handler and give the request to the request handler for processing. On request handler can handle one request at one time, and the server can be configured to start from 1 to a certain desired number of requests handlers to start. As more you have, as more request in parallel can be processed but also, more memory is consumed.
The request handler is itself a seiscomp3 application class application, and so, will read configurations from the seiscomp3 installation folder and from you ~/.seiscomp3 folder. By the default, the name of the configuration file read by the request handler is reqhandler.cfg.
The steps involved in configuring your Arclink server are:
- Load inventory inside your seiscomp3
- Enable the Arclink server
- Tune the arclink server parameters as needed (Optional)
- Tune the request handler parameters as needed (Optional)