Administration: Difference between revisions
| Line 43: | Line 43: | ||
TD.net feed uses MQIPT protocols for message publication and consumption, whilst NRE Darwin subscription utilises a protocol known as STOMP; The gateway server manages the connections to these services and publishes all messages to a message broker, for consumption by the application server(s). | TD.net feed uses MQIPT protocols for message publication and consumption, whilst NRE Darwin subscription utilises a protocol known as STOMP; The gateway server manages the connections to these services and publishes all messages to a message broker, for consumption by the application server(s). | ||
RabbitMQ was chosen as the message broker component within the gateway - all message orientated services on the application servers connect to this broker. | [https://www.rabbitmq.com/ RabbitMQ] was chosen as the message broker component within the gateway - all message orientated services on the application servers connect to this broker. | ||
There are several tools and interfaces provided to administrators for the purposes of monitoring and diagnosing issues with the [gateway server]. | |||
= Application Server = | = Application Server = | ||
Revision as of 15:01, 6 July 2020
This section of the acumen wiki is written for the express purpose of providing information and guidance to acumen administrators.
Simplified Architecture Overview
The application is deployed to 3 servers, as follows:
| Host Name | IP Address | Containerised Deployment? | Purpose |
|---|---|---|---|
| gateway.tms-uk-rail.co.uk | 77.68.28.115 | No | Agregate all inbound message feeds and serve via RabbitMQ Broker to application servers. |
| acumen.tms-uk-rail.co.uk | 77.68.118.126 | Yes | Serve the acumen application (main server) |
| acumen-training.tms-uk-rail.co.uk | 77.68.3.32 | Yes | Serve the acumen application (training server) |
All servers are hired VPS - Virtual Private Server, with the sevice provider being IONOS by 1&1 under several contracts. All servers are located within the UK at a data centre in London.
Gateway Server
The functionality of this component is to aggregate various data feeds and make any resulting messages available to be consumed by one or more application servers.
There are 2 distinct feeds that the gateway server connects to:
- Network Rail TD.net feed;
- National Rail Enquiries Darwin Feed.
TD.net feed uses MQIPT protocols for message publication and consumption, whilst NRE Darwin subscription utilises a protocol known as STOMP; The gateway server manages the connections to these services and publishes all messages to a message broker, for consumption by the application server(s).
RabbitMQ was chosen as the message broker component within the gateway - all message orientated services on the application servers connect to this broker.
There are several tools and interfaces provided to administrators for the purposes of monitoring and diagnosing issues with the [gateway server].