Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Click 'Systemstate'->'Overview of the system state' (At first, only the 'SystemState' link is visible, which leads to the same script, viz. Status/Monitor-JMXsummary.jsp   
  • Check that all internally developed applications are up and running. This depends on the configuration, of course, but there should be
    • One GUIApplication
    • One HarvestJobManagerAppplication
    • One or more HarvestControllerServer. One of these should be HIGHPRIORITY, if you need to run selective/event harvests, and/or
      LOWPRIORITY, if you need to run snapshot harvests

    • One IndexServerIndexServerApplication
    • One or more ViewerProxy applications
    • One WaybackIndexerApplication (optional)
    • One AggregatorApplication (Optional)
    • If you're using the distributed archive solution (ie using the JMSArcrepositoryClient and not the LocalArcRepositoryClient) there should also be
      • One ArcRepositoryApplication
      • One or more BitarchiveServer applications per bitarchive replica in your configuration
      • One ChecksumFileServer ChecksumFileApplication representing a checksum replica (if you have a checksum replica)
      • One BitarchiveMonitorServer for each bitarchive replica in your configuration
  • Check that last status message for each application do not contain errors or warnings
  • Check that there are no empty log messages
  • Click on an physical location in the 'Location' column e.g. "K" (you might need add "location" to the shown columns by clicking on "Location" in the "show:" line just above the column headers.
  • Check that you now only see relevant SW applications for the chosen location
  • Click 'Show all' in the 'Location' header
  • Check that you return to the full listening again
  • Repeat the above 4 steps for "Machine", "HTTP Port", "Application", "Instance Id", "Priority", "Use Replica" and "Index" (Index shows all log lines in the given appl. log)

...