Differences between revisions 4 and 5
Revision 4 as of 2009-10-29 08:03:55
Size: 2854
Editor: TueLarsen
Comment:
Revision 5 as of 2010-01-26 15:58:16
Size: 2801
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
   * No error messages are received at start up
   * The monitoring works
   * The database works and contains test data
Line 8: Line 5:
 * No error messages are received at start up
 * The monitoring works
 * The database works and contains test data
Line 15: Line 15:
Check that JMX works
Line 16: Line 17:
Check that JMX works
  
* Click 'Systemstate'->'Overview of the system state'
   * Check that all internally developed applications are up and running (see applications at KB/SB below)
   * 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" 
   * Check that you now only see relevant SW applications for the chosen organisation
   * Click 'Show all' in the 'Location' header
   * Check that you return to the full listening again
   * Repeat the above 4 steps ’Machine ", "HTTP Port", "Application", "Instance Id", "Priority", "Use Replica" and "Index" (Index shows all log lines in the given appl. log)
     The Instance ID column in the System overview GUI is a technical suffix to the Application column to separate more than one Application of the same type on the same server. If there is only 1 Application on a server it will normally be empty. If there is more than 1 Application of the same type on the same server, there must be added a suffix i.e. an Instance ID. It is userdefined (in the deploy script) and must be unique.
 * Click 'Systemstate'->'Overview of the system state'
 * Check that all internally developed applications are up and running (see applications at KB/SB below)
 * 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"
 * Check that you now only see relevant SW applications for the chosen organisation
 * Click 'Show all' in the 'Location' header
 * Check that you return to the full listening again
 * Repeat the above 4 steps ’Machine ", "HTTP Port", "Application", "Instance Id", "Priority", "Use Replica" and "Index" (Index shows all log lines in the given appl. log)
  . The Instance ID column in the System overview GUI is a technical suffix to the Application column to separate more than one Application of the same type on the same server. If there is only 1 Application on a server it will normally be empty. If there is more than 1 Application of the same type on the same server, there must be added a suffix i.e. an Instance ID. It is userdefined (in the deploy script) and must be unique.
 * Click 'Systemstate' -> 'Overview of the system state'
 * Check that you are back to the full overview with log line 0
Check that basic database data is present
Line 28: Line 31:
   * Click 'Systemstate' -> 'Overview of the system state'
   * Check that you are back to the full overview with log line 0
Check that basic database data is present
   * Click '
Definitions'->'Find Domain(s)'
   * Search for =netarkivet.dk= by writing this text and click 'Search'     * Check that the GUI returns the set-up of domain =netarkivet.dk= without errors
   * Click 'Edit' on the line configuration line for defaultconfig
   * Check that Name is "defaultconfig"     * Check that Harvest template is "default_orderxml"
   * Check that Maximum number of objects is "2.000"     * Check that Maximum number of bytes is "500.000.000"  
 * Click 'Definitions'->'Find Domain(s)'
 * Search for =netarkivet.dk= by writing this text and click 'Search'
* Check that the GUI returns the set-up of domain =netarkivet.dk= without errors
 * Click 'Edit' on the line configuration line for defaultconfig
 * Check that Name is "defaultconfig"
* Check that Harvest template is "default_orderxml"
 * Check that Maximum number of objects is "2.000"
* Check that Maximum number of bytes is "500.000.000"
Line 42: Line 41:
Check that mail recipients specified in the start of this test receive no error mails
   * Check that there are no mails with error messages on non-existing file
   * Check that there are no mails with error messages about applications that could not be started
Check that mail recipients specified in the start of this test receive no error mails
Line 46: Line 43:
---++++Applications at KB/SB:  * Check that there are no mails with error messages on non-existing file
 * Check that there are no mails with error messages about applications that could not be started

==== Applications at KB/SB: ====

Check of monitoring and basic settings

This page describes how to check that

  • No error messages are received at start up
  • The monitoring works
  • The database works and contains test data

Do following in a browser:

Start Program

Check that JMX works

  • Click 'Systemstate'->'Overview of the system state'

  • Check that all internally developed applications are up and running (see applications at KB/SB below)
  • 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"
  • Check that you now only see relevant SW applications for the chosen organisation
  • Click 'Show all' in the 'Location' header
  • Check that you return to the full listening again
  • Repeat the above 4 steps ’Machine ", "HTTP Port", "Application", "Instance Id", "Priority", "Use Replica" and "Index" (Index shows all log lines in the given appl. log)
    • The Instance ID column in the System overview GUI is a technical suffix to the Application column to separate more than one Application of the same type on the same server. If there is only 1 Application on a server it will normally be empty. If there is more than 1 Application of the same type on the same server, there must be added a suffix i.e. an Instance ID. It is userdefined (in the deploy script) and must be unique.
  • Click 'Systemstate' -> 'Overview of the system state'

  • Check that you are back to the full overview with log line 0

Check that basic database data is present

  • Click 'Definitions'->'Find Domain(s)'

  • Search for =netarkivet.dk= by writing this text and click 'Search'
  • Check that the GUI returns the set-up of domain =netarkivet.dk= without errors
  • Click 'Edit' on the line configuration line for defaultconfig
  • Check that Name is "defaultconfig"
  • Check that Harvest template is "default_orderxml"
  • Check that Maximum number of objects is "2.000"
  • Check that Maximum number of bytes is "500.000.000"

Do the following in the appropriate mail program:

Check that mail recipients specified in the start of this test receive no error mails

  • Check that there are no mails with error messages on non-existing file
  • Check that there are no mails with error messages about applications that could not be started

Applications at KB/SB:

See ItXXApplications][Applications at KB/SB

It23JMXMailCheck (last edited 2013-01-03 13:46:13 by SoerenCarlsen)