Download
Getting Started
Members
Projects
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
More
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
Toggle navigation
Bugzilla – Attachment 21487 Details for
Bug 64800
AC 32398 : Provide symptom database editor
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Requests
|
Help
|
Log In
[x]
|
Terms of Use
|
Copyright Agent
Symptom Migration design document
SymptomMigration.doc (text/plain), 27.50 KB, created by
Valentina Popescu
on 2005-05-19 22:08:37 EDT
(
hide
)
Description:
Symptom Migration design document
Filename:
MIME Type:
Creator:
Valentina Popescu
Created:
2005-05-19 22:08:37 EDT
Size:
27.50 KB
patch
obsolete
>ÐÏࡱá>þÿ 24þÿÿÿ1ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿì¥ÁU@ ð¿^bjbj¬¬ "ÎñÎñ^ >ÿÿÿÿÿÿ.......BffffzB þ!!!!!!$Rð FE.E..Zâââ²..âââú¦§0..ghà\ÅfLF×$p0 ûl6!:6!HgBB....6!.g¸âEEBB$fÌBBfSymptom Database migration use case This document describes the user interaction for migrating old symptom databases (WAS format) to the new symptom database format. Scenario: The user had previously installed TPTP 4.0 and had created a runtime workspace with one or more symptom databases and one or more analysis engines. The user now decides to move to a higher version of TPTP, and he installs TPTP 4.1, which contains the new symptom database format. Once he moves to TPTP 4.1, the user expectation is that his old runtime workspace will have exactly the same functionality as it had before, meaning that he would be able to view/update the xmi symptom database (lets call it sdb.sdbxmi) and use the analysis engine implementation to analyze log files. The migration tool should allow the user to perform these tasks. The user chooses to edit the existing sdb.sdbxmi file To do that, he selects the sdb.sdbxmi file in the Eclipse navigator and double clicks on the file. At this point, the default editor should open on the selected resource. A message box is displayed, informing the user that the selected xmi file is an old symptom format. The user is asked if he wants to migrate the file to the new format. If the user answers yes, the migration starts and a new xmi file with extension symptom is created. This file, sdb.symptom, contains the migrated symptom database file. The sdb.symptom file is selected in the navigator and before the editor opens, the user is asked is he wants to remove the old symptom file from the workspace. On yes, the old file, sdb.sdbxmi, is removed. The editor opens on the new xmi file ( sdb.symptom ) and the user can view/update the content. The use wants to analyze log files using his analysis engine and sdb.sdbxmi symptom database file. The user opens a log file into the log view and selects the Analyze action. The available Analyze engine implementations should be visible in the popup action ( ie the old analysis engine implemented by the user using the old symptom database format and any other analysis engines, based on the old or the new symptom database format ) If the user selects to analyze the log using an analysis engine that only understands old symptom database formats, only symptom database in the old WAS format ( extension sdbxmi ) will be used for analysis, and any other (extension symptom)will be simply ignored. If the user selects an analysis engine based on the new symptom database format, old symptom database that were chosen by the user to be used for analysis will be first migrated under the cover to the new format and next will be used in analysis. =A_vz¥¦§¨²C D È Ê á ä > > > >¸ >¹ >ù >:<FMcjrstÃÉÐÜ 6 D R q v üøôðìðìüðüèôáÝÙÝÕÝÑÝÍÉÍÅÍÁ½Á͹͵±µµ¤µµµµµµµµhÐQ®hmt5hÐQ®hÂ'hé01hÿU hÿU hÿU hmtCJh@]hÿU hmth)e%h<¡h5°häSh'"hR'hRhò0h Z6h4Bh/SQh4Bh¬5yhB×hï>8hÈBÀhhahjH6$%§¨²F Ê Ë ú ><=st Ér AB¡¢VúøøøóøøøøøøëæáááááááØëæÏh^hgdX Bh^hgdÕSgdmtgdÿU >&FgdÿU gd/SQgd½)^ý ¤ &4^ ¡ ><AQgn}~UV56abYZ\^üøôøðøìåìáìáìáÝáÝáìÙÕÙìÑøÍÉhjHhÈBÀh-h@hý0éh«qh ÑhÿU hÿU hX Bhé01hzd!hmthÐQ®VWabYZ[\]^ööííèæææægdmth^hgdÕSh^hgdX B 1h°Ð/ °à=!°"°# $ %°D@ñÿDNormalCJ_HaJmH nHsH tHZ@Z½) Heading 1$¤ð¤<@&5CJ KH OJQJ\^JaJ \@\ÿU Heading 2$¤ð¤<@& 56CJOJQJ\]^JaJDA@òÿ¡DDefault Paragraph FontRi@óÿ³RTable Normalö4Ö >l4Öaö(k@ôÿÁ(No List<m@Äñ<ÿU 1 / 1.1 / 1.1.1FªI@ª/SQMessage Headerg8Èû$d%d&d'd-DMÆ >ÿÿNÆÿOÆÿPÆÿQÆÿ^8`ÈûOJQJ^JV>@V/SQTitle$¤ð¤<@&a$5CJ KHOJQJ\^JaJ ^ >ÿÿÿÿ$%§¨²FÊËú<=st ÉrAB¡¢VWa b Y >Z >[ >\ >] >` >000000¨0¨0¨0¨0¨0¨ 00=0=0=0=0=0=0=0=0 00x0000000000 ^ > V^^cmad8Cv(2^ait¡¡ãí§© ` >¥¬27gt ¢¥©` >3333~¬B¡¡` >¡¡` >ÿÿLabuser|ÿÿÿ´!^´ÿÿÿÿÿÿÿÿÿ}ÿÿÿp¼³ÿÿÿÿÿÿÿÿÿ~ÿÿÿî·ò¨ÿÿÿÿÿÿÿÿÿÿÿÿ{TjÿÿÿÿÿÿÿÿÿÿÿÿI(Rÿÿÿÿÿÿÿÿÿÿÿÿ¾*NÿÿÿÿÿÿÿÿÿÿÿÿRèÿÿÿÿÿÿÿÿÿÿÿÿþê ÿÿÿÿÿÿÿÿÿÿÿÿP|Â,ÿÿÿÿÿÿÿÿÿÿÿÿé¶ÿÿÿÿÿÿÿÿÿ8|H ÿÿÿÿÿÿÿÿÿdUA ÿÿÿÿÿÿÿÿÿ)_ºD ÿÿÿÿÿÿÿÿÿExN6_bÿÿÿÿÿÿÿÿÿôpd´ÿÿÿÿÿÿÿÿÿþÆ^`þ. þÆ ^ `þ.8þÆ8^8`þ.ÐþÆÐ^Ð`þ.þÆ^`þOJQJo(·ð þÆ ^ `þOJQJo(·ð8þÆ8^8`þOJQJo(·ðÐþÆÐ^Ð`þOJQJo(·ðhþÆh^h`þ.hþÆh^h`þOJQJo(·ð >hþÆh^h`þhH. >PþÆ^`PþhH.. >ÈþÆ ^È`þhH... >ÀxýÆp^À`xýhH.... >¸èüÆØ ^¸`èühH >..... >° >Xüƨ^° >`XühH...... >¨ÈûÆ^¨`ÈûhH....... > 8ûÆà^ `8ûhH........ >à`úÆ°^à``úhH......... >hþÆh^h`þhH. >PþÆ^`PþhH.. >ÈþÆ ^È`þhH... >ÀxýÆp^À`xýhH.... >¸èüÆØ ^¸`èühH >..... >° >Xüƨ^° >`XühH...... >¨ÈûÆ^¨`ÈûhH....... > 8ûÆà^ `8ûhH........ >à`úÆ°^à``úhH......... >hþÆh^h`þhH. >PþÆ^`PþhH.. >ÈþÆ ^È`þhH... >ÀxýÆp^À`xýhH.... >¸èüÆØ ^¸`èühH >..... >° >Xüƨ^° >`XühH...... >¨ÈûÆ^¨`ÈûhH....... > 8ûÆà^ `8ûhH........ >à`úÆ°^à``úhH.........hÐþÆÐ^Ð`þo(.h > þÆ ^ `þhH.h >pLÿÆp^p`LÿhH.h >@þÆ@^@`þhH.h >þÆ^`þhH.h >àLÿÆà^à`LÿhH.h >°þÆ°^°`þhH.h >þÆ^`þhH.h >PLÿÆP^P`LÿhH.ÐþÆÐ^Ð`þo(. > þÆ ^ `þhH. >pLÿÆp^p`LÿhH. >@þÆ@^@`þhH. >þÆ^`þhH. >àLÿÆà^à`LÿhH. >°þÆ°^°`þhH. >þÆ^`þhH. >PLÿÆP^P`LÿhH.ôpExNdUA8|H)_ºDÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ~ÿÿÿ}ÿÿÿ|ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ (å'ò0«qRjHÿU @+Yha-zd!)e%Â'R'½)é01 Z6ï>8X B4B/SQäS<IWÖnsmtî_x¬5yÕS@]'"4<¡wªÐQ®5°t9´ÈBÀ ÑB×cçý0éÿ@¡¡@|¡¡^ >°@ÿÿUnknownÿÿÿÿÿÿÿÿÿÿÿÿGz ÿTimes New Roman5Symbol3&z ÿArialG5 > ¿ ûüÇhMS Mincho-ÿ3ÿ fg"1ðÐhK "4ÒÒ!ð ´´4Y >Y >@ðHðÿäÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿî_xÿÿLabuserLabuserH > þÿà òùOh«+'³Ù0T¨¸ÄØ èô > (4<DLässLabuserabuNormal.dotLabuser34uMicrosoft Word 10.0@8ªC@*¶ÈØ\Å@îæSà\ÅÒþÿÕÍÕ.+,ù®0èhp|¤¬´ ¼ÉäIBMY >O >Title > þÿÿÿ þÿÿÿ"#$%&'(þÿÿÿ*+,-./0þÿÿÿýÿÿÿ3þÿÿÿþÿÿÿþÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿRoot Entryÿÿÿÿÿÿÿÿ ÀF`Êhà\Å51Tableÿÿÿÿÿÿÿÿ~!WordDocumentÿÿÿÿÿÿÿÿ"SummaryInformation(ÿÿÿÿ!DocumentSummaryInformation8ÿÿÿÿÿÿÿÿÿÿÿÿ)CompObjÿÿÿÿÿÿÿÿÿÿÿÿjÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿþÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿþÿ >ÿÿÿÿ ÀFMicrosoft Word Document >MSWordDocWord.Document.8ô9²q
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 64800
: 21487