Cegal Hub Server runs as a stand-alone server on Windows or Linux or within containers.
For more detailed information please check the Hub Server options in Hub Server options or go to the tutorials for some examples.
Communicating with Hub Server#
Once a Cegal Hub Server is running, both “connector” applications and “client” applications can communicate with Hub Server.
Hub Server acts as a proxy for this communication and allows “client” requests to be made on “connectors” which register a set of functionality with the Hub Server.
This communication can be made within the same machine or across the local or public cloud network.
Restricting Cegal Hub Server to tenant users only#
If Cegal Hub Server is running in a public setting its important to ensure only users from your Keystone tenant are able to access the tenant.
To find you keystone tenant, use the Hub commandline utility with the following command.
cegalhub keystone tenant-id
When running the server ensure you include the keystone-tenant-id flag
./cegalhub server --keystone-tenant-id=<the_value_above>
Monitoring Hub Server with Prometheus#
Cegal Hub Server supports monitoring via Prometheus. Hub Server offers and http endpoint for Prometheus metrics.
This endpoint can be scraped by Prometheus and allows collection of standard Golang metrics in addition to some custom Hub Server metrics.
Hub Server must be run with the Prometheus flags enabled.
./cegalhub server --prometheus --prom-port=<port>
Running Hub Server as a service#
Cegal Hub can be installed as a service of Windows or Linux.
Activating a Cegal Hub Server#
When running in server mode a Cegal Hub server must be activated before it accepts connections.
To activate a running server use the Hub commandline client.
cegalhub client activate --address=cegalhub.demo1-ispace.cegal-geo.com --port=443 --tls