...

There are 5 main applications to be split across any given environment. The split occurs as follows (Prod 01 environment used in the examples):
prod-dboard01-trap.geant.net

• Trap Processor application (JAR) (TrapProcessor / dashboard-fs-trap-processor)

prod-dboard01-corr.geant.net

• Correlator application (WAR in tomcat) (dashboard-fs-correlator)
• Network Map Populator application (JAR) (populate-web / dashboard-networkdb-repopulator)

prod-dboard01.geant.net

• Web Application (WAR in tomcat) (dashboardV2)
• OTRS application (WAR in tomcat) (otrs-messaging)

There is also a small 6th application, which sits on the Production OpsDB 01 box (prod-opsdb01.geant.net), whose purpose is to periodically (or on demand) provide updated versions of OpsDB for network map population. There are unlikely to be many (if any) new versions of this particular application, so it is unlikely to be necessary to deploy it regularly.

Anchor
_Toc446088702 _Toc446088702

Server Set-up

...

Please consult the original ticket raised for the set up of the Dashboard machines for details of software required, but in addition to any standard pre-requisities and as a bare minimum the machines should have (in each case, the version should be the one currently on UAT, except for the Nginx exception listed below):
prod-dboard01-trap.geant.net

• JDK 8 (Oracle version)
• Active MQ local instance If using the version of the trap processor which requires a local mq instance

prod-dboard01-corr.geant.net

• JDK 8 (Oracle)
• Apache Tomcat 7
• MySQL Server

prod-dboard01.geant.net

• JDK 8 (Oracle)
• Apache Tomcat 7
• Nginx (version should be that on the redundant test-newdboard01.geant.net server)

...

The following databases should be present on the correlator box:

• alarms2
• networkmap
• maintenance
• router_population
• opsdb

...

The OpsDBCopier application is currently logging to dante.sanigar/copier.log (but the file can be changed whenever the application is restarted).

Anchor
_Toc446088728 _Toc446088728

RPM Repositories

...