Deployment¶

Current Deployment¶

All access to the Configuration Database (heplnm069) is via micewww (heplnm068)

Micewww (heplnm068)¶

An Apache web server is listening on port 8080
Tomcat is listening on port 4443

Requests to 8080/api are redirected to Tomcat on port 4443

In order to process requests Tomcat accesses the Configuration Database on heplnm069

Configuration Database Machine (heplnm069)¶

The configuration database is in Postgres

Micenet Online Machine¶

This uses the CDB API to read and write to the Configuration Database via Tomcat on Micewww

Suggestion for Future Deployment¶

Micewww (heplnm068)¶

As above, but only read only access to the Configuration Database Machine (heplnm069)

Configuration Database Machine (heplnm069)¶

The configuration database is in Postgres
Postgres configured to only accept read requests from micewww
Write access to Postgres is via a local Tomcat server and a copy function from Master Configuration Database on Micenet

The Tomcat server is configured to only accept requests from Micenet

Micenet Master Configuration Database (new machine)¶

This will be configured the same as the Configuration Database Machine (heplnm069) expect:

• it will act as the master database and copy data to the Configuration Database Machine (heplnm069)
• it will only accept connections from mice net

Micenet Online Machine¶

This will use the CDB API to read and write to the Micenet Master Configuration Database
In the event of a failure of the Micenet Master Configuration Database a configuration file would be manually changed to point to the Configuration Database Machine (heplnm069)