Community
Participate
Working Groups
Summary: #32398 Tracker: Feature Requests Description: Provide symptom database editor based on the new ACAB symptom format
*** Bug 64794 has been marked as a duplicate of this bug. ***
This work was done outside of TPTP and the requirement here is to contribute it into TPTP 4.0 since it is breaking api.
Update target and priority based on TPTP Features for 3.2+ document Alex, please confirm with Eric, Chris that this is required for TPTP 3.3
Updating feature target per 01/10 UI main committers meeting
Eugene requires this defect to be moved to 4.0 i2; to be discussed in the rol up call
update component
Required to be moved to 4.0 - based on the new sbd spec
Finished.
*** Bug 50762 has been marked as a duplicate of this bug. ***
moving to 4.1
Created attachment 21487 [details] Symptom Migration design document
moving target to 4.2 per Chris's request
1. Create EMF model for Symptom specs 2. Provide an extension point for correlation rule in the symptom db editor 3. Create version of Symptom specs (XSD/XML) 4. Provide an extension point for symptoms rule in the symptom db editor 5. Provide transform from old WAS format to Symptom 1.1 format 6. Provide symptom database example
The symptom editor needs to be a standalone plugin(s) with no dependency on GLA, RAC, LTA, etc. - we'll want to make this available as a downloadable plugin. The only acceptable dependency is on the model plugin
Placeholder to remember that terminology for symptoms has changed and needs to be reflected in the UI (editor and views) and docs wherever required for 4.2 The symptom editor needs to be a standalone plugin(s) with no dependency on anything else like GLA, RAC, LTA, etc. - want to make this available as a downloadable plugin.
Theme: Design for Extensibility: Be a Better Platform
Candidate for 4.2
For LTA 4.2, TPTP feature 64800 will include a conversion utility to convert old TPTP symptom databases to the new TPTP symptom format to make this migration from the old format to the new format transparent to the user.
Note that the migration utility will not be run transparently Open the design document for a detailed description of the migration scenario
On top of the content of the symptom migration document, this works consists of updating the TPTP symptom database editor to the new symptom definition format. This editor will allow to specify all the symptom definition properties and provide extension points to: -add other rule editor based on any symptom rule format. TPTP will provide an implementation of this extension point for the XPATH rules -add a validation extension point so the user can provide an implementation for validating their symptom rule. The TPTP implementation of this extension point will display the validation errors into the symptom editor. Also, TPTP will need to provide an XPATH rule editor inside the symptom editor. Some type of code assist function will be part of the XPATH rule editor. TPTP will need to provide an extension point in the File->Export Symptom Catalog in order to allow to export Symptom catalog in the ACAB Symptom 2.0 format. This TPTP implementation of the extension point will allow to export Symptom catalogs into XML format with the XPATH rules. TPTP will continue to give the option to the user to export in the old TPTP formats. TPTP will need to provide an extension point in the File->Export Symptom Catalog in order to allow to import Symptom catalog in the ACAB Symptom 2.0 format. This TPTP implementation of the extension point will allow to import Symptom catalogs into EMF with the XPATH rules. TPTP will continue to give the option to the user to import in the old TPTP formats. TPTP will rename menu items for the symptom editor based on the new symptom specs.
The migration scenario sounds fine. Is it possible to have a check box on the initial message to let the user indicate they want the old .sdbxmi file deleted? That way, the migration can be done and the new one opened immediately for editing.
Alex, please open point features for the work that will be delivered in i1 ( if any )
Closing. Creating a new sample for editor extensions will be done as part of https://bugs.eclipse.org/bugs/show_bug.cgi?id=134556.
close bug
