System validation
Validation steps have been included within this guides in sections to help ensure function verification checks occurs prior to commencing any further activities. To ensure the solution is functioning as it correctly, the following final high-level checks should be completed.
- Traffic flows through all pipelines (HBR main - HBR child - Canister) when injecting a test session using the Discover Archive Reader utility.
- The resulting session can be found as an active session immediately after being injected.
- The resulting session moves from a status of active session to being completed after the default timeout of 5 minutes.
- Events fire on that session.
- Privacy rules are working.
- The session should replay in either the Advanced or Event based replay UI.
- Any count resulting from events firing for that session (including OOO hit counts) resulting from that test session should appear in reports and dashboards.
- The eventdefs.xml is generated on the Processing servers in
<Discover_Home_Folder>\System\eventdefs.xml. - All Discover servers (Master, HBR, Processing) appear on the DMS page (in green status).
- All Discover servers (Master, HBR, Processing) appear on the 'Manage Servers' page.
- Creating and saving a new event succeeds.
- Historical data is displayed in reports (if any).
- All servers are defined in the back-end SQL Server database, in the TM_SERVER table.
- All services are defined in the back-end SQL Server database, in the TM_SERVICE_MAP table.
- After the go-live, the security team is sought to perform an audit of the platform with the objective of achieving operational excellence.
Success
Your environment should now be available.