Community
Participate
Working Groups
The Export Log Set dialog cannot be extended. We would like to be able to extend the export log set dialog in one of the following ways: 1. Add a drop down list to the main dialog page to select target for export, i.e. localhost, or some other host from a list. OR 2. Configure the default export location, i.e. when the user clicks the Browse button, the Open dialog opens to a directory that can be configured through a properties file or some other means of configuration.
The Import Log set dialog should be extendable as well, with the same capabilities as the export log set dialog, e.g. 1. add a button on the import log dialog to import from a location other than local machine
Require a single extension point to modify the Import log set dialog Import Log Set Export Log Set -- extension point will allow both these options to launch the LDS wizard Finish -- extension point will allow a custom finish action to be specified.
Side note: In the finish action, we need to be able to kick off launch in context, and do some directory clean-up as well.
Add me in cc
------- Comment #12 From Praful Rajawat 2006-12-22 11:32:27 [reply] ------- Host name should be configurable if needed by the tooling. If log is transfer by tooling from the remote host to local host by any other file transfer method and then all the processing is done on the local host, there should be a way to add that log/s to remote host node in the navigator. This is also applies to the FTP transfer log from the remote machine and then import locally in the tooling, but host node should be with remote host name. This is very important because then delta time (Time offset) can be apply based on host. With the current implementation delta time offset can not apply correctly because all the remote logs are added in local host node. Also there should be a way to enable/disable the host name TAB in the import wizard. Need UCD input on this how actually this would look like in above scenarios ------- Comment #13 From Jeff Calcaterra 2006-12-22 12:33:04 [reply] ------- (In reply to comment #12) I am going on vacation for the week after today, so we should talk before I leave if possible. > Host name should be configurable if needed by the tooling. I don't understand this comment. In the design I sent users can change the name. Are you saying the tooling should be able to do this automatically from the context file? > If log is transfer by tooling from the remote host to local host by any other > file transfer method and then all the processing is done on the local host, > there should be a way to add that log/s to remote host node in the navigator. > This is also applies to the FTP transfer log from the remote machine and then > import locally in the tooling, but host node should be with remote host name. > This is very important because then delta time (Time offset) can be apply based > on host. With the current implementation delta time offset can not apply > correctly because all the remote logs are added in local host node. > Also there should be a way to enable/disable the host name TAB in the import > wizard. > Need UCD input on this how actually this would look like in above scenarios > I understand what you are asking in general, but am confused about a lot of the details. Basically: 1. Where the filtering is done depends on the protocol used for transfering files. 2. This also affects the delta time filtering. I do not see where this stuff is done in the current LTA Eclipse. Can users select the protocol? I don't see the time skew either. Are you talking about the default TPTP part or some of the IBM extensions? ------- Comment #14 From Praful Rajawat 2006-12-22 12:47:08 [reply] ------- I am talking about the default TPTP part. Currently in TPTP user can add delta time per log and/or per host. If log is imported by other means like FTP but not using RAC, log is added in the Local host node. SO now if user wants to apply the delta time to that log, user needs to apply on perticulare log. User can't apply delta time to host which may not be valid in this case.
Created attachment 57747 [details] description doc
Nellie, Malcom and I reviewed the design doc. This design document reflects what we need.
Created attachment 58034 [details] Updated feature document Updated the symptom catalog URL capturing requirement and provided a simpler solution.
This feature has been reviewed by the AG group on Feb 2, 2007 Attendees: Alex, Euegene, Dave, Joanna Review result: AG approved, pending the following updates to the design document Point 6 in the requirement summary should be updated. There is no need for the Import symptom catalog wizard to capture the symptom information in a preference file. Instead of this, the symptom URL attribute will be used to capture the symptom location before being imported into the workspace. Eugene will make this change
Please set target to 4.4, priority to P1, and add sizing.
Removing 4.4 target until this feature is formally approved by PMC.
Adjusting target to reflect plan taken forward for approval
In my opinion, sourceComponentId.location should be used to set the virtual host name so delta time can be updated correctly. In case for FTP file transfer, if 2 different logs are been move to ftp server from 2 different remote server, and approach in feature document is applied, it will provide in wrong information since both remote host may have different delta time.
Alex, I am assigning this to you as the owner as discussed.
Function checked in.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
