GSI - BEA Wiki

User Tools

Site Tools

Trace:
projects:bpm-sis18:status

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Last revision Both sides next revision
projects:bpm-sis18:status [2012/07/12 18:46]
rhaseitl 		projects:bpm-sis18:status [2012/07/12 19:00]
rhaseitl
Line 22: Line 22:
   * connection to BPM established/lost/reconnected   * connection to BPM established/lost/reconnected
   * debug output at every status change of the system (Initializing, Start, Stop,...)   * debug output at every status change of the system (Initializing, Start, Stop,...)
 +  * logging should use the Log4j framework (from within the FESA class possible with SDLog (HBr))
 +  * the GUI should **not** encapsulate exceptions thrown by cmw / rda into its own Exception class (HBr)
 +  * a detailed documentation of the meaning and reasns for each error message, exception etc. should be made (HBr)
  
 \\ \\
Line 44: Line 47:
   * Display the connection status and if a command which has been sent, was "acknowledge" by the PTIF. Can give a hint, when the PTIF seems to be reachable by TCP/IP but the FESA class is not sending commands. Test case: Pull network cable and reconnect. System should be able to detect this, if the PTIF cannot be controlled afterwards.   * Display the connection status and if a command which has been sent, was "acknowledge" by the PTIF. Can give a hint, when the PTIF seems to be reachable by TCP/IP but the FESA class is not sending commands. Test case: Pull network cable and reconnect. System should be able to detect this, if the PTIF cannot be controlled afterwards.
  
-**Would it make sense to have a simple standalone tool to see if the FESA servers, the BPMs, the gen servers are up and running without an error flag?! In principle this information is provided by the default status panel, but you have to be an expert to interpret some errors. There might be a button to query all devices. **+Have a standalone tool to see ALL system components directly: FESA server classes, CCCPs, Liberas (pingable), the gen servers (are up and running?), show error flags. It might be a good idea to have a button for each component to perform a check. E.g. perform a ping for the Liberas and CCCPs. Or perform a data query from the FESA classes. 
 +Some of this information is provided by the detailed status panel, but you have to be an expert to interpret some errors. 
  
-Yes, I think it does! (HBr) 
  
 == Goals == == Goals ==
Line 53: Line 56:
 Provide tools to observe the health status of the system components. Provide tools to observe the health status of the system components.
  
-Some issues (HBr): +
-  * logging should use the Log4j framework (from within the FESA class possible with SDLog (HBr)) +
-  * the GUI should **not** encapsulate exceptions thrown by cmw / rda into its own Exception class +
-  * a detailed documentation of the meaning and reasns for each error message, exception etc. should be made+
  
 Some more considerations (MSchw): Some more considerations (MSchw):
projects/bpm-sis18/status.txt · Last modified: 2012/07/13 09:11 by klang

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki