<?xml version="1.0" encoding="UTF-8" ?> 
<welcomePage title="Hyades Project" format="wrap">
	<intro>
	Hyades is an integrated test, trace and monitoring environment, that provides standards, tools and tool interoperability across the test process.
	This page will help familiarize you with the Hyades project. To get started, read the sections below and click on the related links. </intro>
	
	<item><b>Profiling an application </b>
To profile an application open to the Profiling and Logging Perspective <action pluginId="org.eclipse.hyades.trace.ui" class="org.eclipse.hyades.trace.ui.internal.actions.OpenProfilePerspectiveAction">Window > Open Perspective > Profiling and Logging</action>.
The tool allows you to launch and profile an application on the localhost or a remote machine, and to attach to an already running application and start collecting profiling data. There are a set of user interface controls which allows you to interact with the application being profiled such as run garbage collection, collect object reference information, attach, detach, start or stop monitoring, update profiling filters and options. 
Use the profiling statistical and graphical views to analyze the information.Use profiling statistical views to identify performance hot spots, Object Reference table to find memory leaks and Execution graphs to find execution problems. 
    </item>

	<item><b>Log browsing </b>
It is possible to import logs that are stored on either the local machine or remote machines. To start browsing an existing log file, first import the file into the workspace using the File > Import ... > Log File action. The import wizard allows you to select the machine, producer of the log, and log file instance. For remote machines, you will need to have the RAC installed on the remote machine to process the log.
</item>

	<item><b>Log analysis </b>
Once you have imported a log file into the workbench you can browse the data and analyse the information. To do that, open the <action pluginId="org.eclipse.hyades.trace.ui" class="org.eclipse.hyades.trace.ui.internal.actions.OpenProfilePerspectiveAction">Profiling and Logging</action> Perspective and show the file using the Log view. Next, import a symptom database file into the workspace using File > Import... >Symptom Database File action. Use Analyse popup action on the Log view to analyse the log data using this symptom database.
     </item>

	<item><b>Correlating log files </b>
Import into the workspace the log files you want to correlate.

Select one or more log agents in the Log Navigator view and create a new Log Correlation by right-clicking, 
then selecting New > Log Correlation > Profiling and Logging > Log Correlation.
To view the Log Interactions, right-click on the newly created correlation, 
and select Open With > Log interactions.

Alternative method:
In the Profiling Monitor view, make the Monitor object visible using the
<action pluginId="org.eclipse.ui" class="org.eclipse.ui.internal.OpenPreferencesAction">Window >Preferences</action> wizard. Select Profiling and Logging >Profiling Monitor view
preference page.
From the Profiling Monitor view in Profiling and Logging perspective, select the Monitor object 
then choose Open With > Log interactions action. Select the type of correlation you
want to use. All log files under the Monitor object, supporting this type of
correlation, will participate in correlation.
     </item>
     
	<item><b>Symptom database </b>
A symptom database is an XML file that is used to store events and errors with any possible reasons for the events and any possible solutions for the errors. Import a symptom database from the localhost or a remote host using File > Import... >Symptom Database File action. Use <action pluginId="org.eclipse.ui" class="org.eclipse.ui.actions.NewWizardAction">File > New > Other... > Symptom Database</action> to create a new symptom database file. Open the log file you want to analyse in the Log view, then use the Analyse or Analyse All Log view popup action to analyse a subset or all of the log records.
     </item>
     
</welcomePage>
