|
TPTP 4.4.0 Monitoring Tools Project Public API Specification |
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||||
java.lang.Objectorg.eclipse.hyades.sdb.analysis.AnalysisEngine
Implementation of the IAnalysisEngine interface.
This class provides a static API to retrieve a new instance of an AnalysisEngine.
An Analysis Engine instance uses one symptom database to
search for zero or more Directive(s) based
on zero or more Incident matches.
The symptom database is loaded into an EMF model structure from a predefined formatted XML file. The symptom database may be reloaded/merged/removed/replaced.
Usage:
AnalysisEngine analysisEngine = AnalysisEngine.getInstance(symptomDBPath) Object[] analysis = analysisEngine.analyze(incident);
| Method Summary | |
|---|---|
java.lang.Object[] |
analyze(org.eclipse.hyades.analysis.engine.Incident incident)
The current symptom database is searched for Incident matches.
|
org.eclipse.hyades.analysis.engine.Solution[] |
analyzeForSolutions(org.eclipse.hyades.analysis.engine.Incident incident)
The current symptom database is searched for Incident
matches.
|
static AnalysisEngine |
getInstance()
Static API to retrieve a new instance of an AnalysisEngine without an associated symptom database. |
static AnalysisEngine |
getInstance(java.lang.String symptomDbPath)
Static API to retrieve a new instance of an AnalysisEngine. |
java.lang.String |
getSymptomDatabasePath()
Returns the XMI file path of the base symptom database. |
boolean |
mergeSymptomDatabase(java.lang.String symptomDbPath)
Loads a new symptom database XMI file denoted by the parameter path and merges any unique records with the base symptom database |
boolean |
reloadSymptomDatabase()
Reloads the base symptom database from the base symptom database XMI file. |
boolean |
removeSymptomDatabase()
Removes the base symptom database. |
boolean |
replaceSymptomDatabase(java.lang.String symptomDbPath)
A new XMISymptomDB symptom database is created. |
| Methods inherited from class java.lang.Object |
|---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Method Detail |
public static AnalysisEngine getInstance()
NOTE: A base symptom database may be added using
replaceSymptomDatabase(symptomDbPath).
replaceSymptomDatabase(String)public static AnalysisEngine getInstance(java.lang.String symptomDbPath)
symptomDbPath - the path to the symptom database XMI file
public boolean reloadSymptomDatabase()
reloadSymptomDatabase in interface org.eclipse.hyades.analysis.engine.IAnalysisEnginepublic boolean mergeSymptomDatabase(java.lang.String symptomDbPath)
mergeSymptomDatabase in interface org.eclipse.hyades.analysis.engine.IAnalysisEnginesymptomDbPath - the path to the merged symptom database XMI file
public boolean removeSymptomDatabase()
NOTE: A base symptom database may be added using
replaceSymptomDatabase(symptomDbPath).
removeSymptomDatabase in interface org.eclipse.hyades.analysis.engine.IAnalysisEnginereplaceSymptomDatabase(String)public boolean replaceSymptomDatabase(java.lang.String symptomDbPath)
If the new symptom database XMI file was successfully loaded, it replaces the base symptom database.
replaceSymptomDatabase in interface org.eclipse.hyades.analysis.engine.IAnalysisEnginesymptomDbPath - the path to the symptom database XMI file
public java.lang.String getSymptomDatabasePath()
If no base symptom database is loaded, null is returned.
getSymptomDatabasePath in interface org.eclipse.hyades.analysis.engine.IAnalysisEnginepublic java.lang.Object[] analyze(org.eclipse.hyades.analysis.engine.Incident incident)
Incident matches.
All Directive(s) from successful Incident
matches are returned in an array structure.
Incident matches are based on a lexicographical String
comparison between the messageId in the parameter
Incident and the value attribute of the
matchPattern Node in the base symptom database.
analyze in interface org.eclipse.hyades.analysis.engine.IAnalysisEngineincident - the search criteria used for possible matches
Directive from successful Incident matchesDirective,
Incidentpublic org.eclipse.hyades.analysis.engine.Solution[] analyzeForSolutions(org.eclipse.hyades.analysis.engine.Incident incident)
Incident
matches.
All Solution(s) from successful Incident
matches are returned in an array structure.
Incident matches are based on a lexicographical String
comparison between the messageId and rawData
array in the parameter Incident and the value
attribute of the matchPattern Node in the base symptom
database.
analyzeForSolutions in interface org.eclipse.hyades.analysis.engine.IAnalysisEngineincident - the search criteria used for possible matches
Solution from successful Incident matchesSolution,
Incident
|
TPTP 4.4.0 Monitoring Tools Project Public API Specification |
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | ||||||||||