Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Equinox Resource Monitoring Demo"
(→Workspace Resources) |
|||
Line 1: | Line 1: | ||
− | + | ==Server Setup== | |
− | + | ||
− | + | ||
* Install the server zip file into an Eclipse SDK (tested with build I0228-0930). | * Install the server zip file into an Eclipse SDK (tested with build I0228-0930). | ||
* Note you can set port and protocol via System properties (but we won't). | * Note you can set port and protocol via System properties (but we won't). | ||
Line 16: | Line 14: | ||
** Close the Preferences window. | ** Close the Preferences window. | ||
− | + | ==Client== | |
* Install the client zip file into an Eclipse SDK (tested with build I0228-0930). | * Install the client zip file into an Eclipse SDK (tested with build I0228-0930). | ||
* Start the SDK. | * Start the SDK. | ||
Line 26: | Line 24: | ||
* <em>Note:</em> The <em>Contributions View</em> will be populated with the available contributions from the server. | * <em>Note:</em> The <em>Contributions View</em> will be populated with the available contributions from the server. | ||
− | + | ===Bundles=== | |
* In the <em>Contributions View</em>, expand the <em>Bundles</em> element. | * In the <em>Contributions View</em>, expand the <em>Bundles</em> element. | ||
** <em>Note:</em> These are all the bundles that are installed on the server. | ** <em>Note:</em> These are all the bundles that are installed on the server. | ||
Line 37: | Line 35: | ||
*** <em>Note:</em> there are 3 different icons, one each for providing, using, and both. | *** <em>Note:</em> there are 3 different icons, one each for providing, using, and both. | ||
− | + | ===Extension Registry=== | |
* In the <em>Contributions View</em> expand the <em>Extension Points</em> element. | * In the <em>Contributions View</em> expand the <em>Extension Points</em> element. | ||
** <em>Note:</em> All the extension points are listed. | ** <em>Note:</em> All the extension points are listed. | ||
Line 45: | Line 43: | ||
* <em>Future work:</em> add extensions, namespaces, better grouping, and more methods. | * <em>Future work:</em> add extensions, namespaces, better grouping, and more methods. | ||
− | + | ===Preferences=== | |
* In the <em>Contributions View</em> expand the <em>Preferences</em> element. | * In the <em>Contributions View</em> expand the <em>Preferences</em> element. | ||
* Expand to <em>Preferences -> instance -> org.eclipse.core.resources</em>. | * Expand to <em>Preferences -> instance -> org.eclipse.core.resources</em>. | ||
Line 56: | Line 54: | ||
** <em>Note:</em> The <em>Build Automatically</em> preference is now unchecked. | ** <em>Note:</em> The <em>Build Automatically</em> preference is now unchecked. | ||
− | + | ===Services=== | |
* In the <em>Contributions View</em> expand the <em>Services</em> element. | * In the <em>Contributions View</em> expand the <em>Services</em> element. | ||
* Expand the <code>org.eclipse.core.runtime.IExtensionRegistry</code> element. | * Expand the <code>org.eclipse.core.runtime.IExtensionRegistry</code> element. | ||
* Expand the <em>Bundles</em> element and see who is importing the service, exporting the service, and both. | * Expand the <em>Bundles</em> element and see who is importing the service, exporting the service, and both. | ||
− | + | ===Sleak=== | |
* expand Sleak | * expand Sleak | ||
* TODO why don't these numbers look right?? | * TODO why don't these numbers look right?? | ||
− | + | ===VM=== | |
* In the <em>Contributions View</em> expand the <em>VM Stats</em> element. | * In the <em>Contributions View</em> expand the <em>VM Stats</em> element. | ||
* <em>Note:</em> All the VM info is for the VM currently running the server. | * <em>Note:</em> All the VM info is for the VM currently running the server. | ||
− | + | ===Workspace Resources=== | |
* In the <em>Contributions View</em> expand the <em>Workspace Resources</em> element. | * In the <em>Contributions View</em> expand the <em>Workspace Resources</em> element. | ||
* <em>Note:</em> The Equinox projects that you previously imported into the server's workspace should be in the list. | * <em>Note:</em> The Equinox projects that you previously imported into the server's workspace should be in the list. | ||
Line 78: | Line 76: | ||
* <em>Note:</em> The launcher fragment project was deleted from the server's workspace. | * <em>Note:</em> The launcher fragment project was deleted from the server's workspace. | ||
− | + | [[Category:Equinox]] | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + |
Revision as of 14:34, 2 March 2007
Contents
Server Setup
- Install the server zip file into an Eclipse SDK (tested with build I0228-0930).
- Note you can set port and protocol via System properties (but we won't).
- Start the SDK.
- The server will start automatically.
- Create resources in the workspace.
- File -> Import -> Plug-ins and Fragments -> Import As Projects with source folders
- Type
org.eclipse.equinox.*
in the filter to get all the Equinox projects selected and choose Add - Finish.
- Note: The Equinox projects appear in the workspace
- Look at a preference value.
- Window -> Preferences -> General -> Workspace -> Build Automatically
- Note: the auto-build preference is set to be true.
- Close the Preferences window.
Client
- Install the client zip file into an Eclipse SDK (tested with build I0228-0930).
- Start the SDK.
- Switch perspectives and create a connection to the server.
- Window -> Open Perspective -> Other -> JMX Resource Management
- JMX Server -> Open Connection
- Choose proper host, port and protocol. (default is localhost, 8118, and rmi)
- OK.
- Note: The Contributions View will be populated with the available contributions from the server.
Bundles
- In the Contributions View, expand the Bundles element.
- Note: These are all the bundles that are installed on the server.
- Expand
org.eclipse.equinox.registry
.- Note: The imported packages and required bundles are listed as well as the services.
- Expand the imported packages to show what it requires.
- Expand the required bundles to show what it requires.
- Expand
org.eclipse.equinox.common
to show it is recursive.
- Expand
- Expand Services.
- Note: there are 3 different icons, one each for providing, using, and both.
Extension Registry
- In the Contributions View expand the Extension Points element.
- Note: All the extension points are listed.
- Navigate to the
org.eclipse.runtime.applications
extension point- Note: All of the available applications should be there, including the JMX server application and the IDE application.
- TODO: Can we hook in Tom's demos here? click on an extension and start it remotely?
- Future work: add extensions, namespaces, better grouping, and more methods.
Preferences
- In the Contributions View expand the Preferences element.
- Expand to Preferences -> instance -> org.eclipse.core.resources.
- Select the
org.eclipse.core.resources
node. - In the Operations part of the editor, select the
put
operation. - In Invocation View, set the parameters to be the key
description.autobuilding
and the valuefalse
. - Select the Invoke button.
- Look at the preference on the server.
- On the server choose: Window -> Preferences -> General -> Workspace.
- Note: The Build Automatically preference is now unchecked.
Services
- In the Contributions View expand the Services element.
- Expand the
org.eclipse.core.runtime.IExtensionRegistry
element. - Expand the Bundles element and see who is importing the service, exporting the service, and both.
Sleak
- expand Sleak
- TODO why don't these numbers look right??
VM
- In the Contributions View expand the VM Stats element.
- Note: All the VM info is for the VM currently running the server.
Workspace Resources
- In the Contributions View expand the Workspace Resources element.
- Note: The Equinox projects that you previously imported into the server's workspace should be in the list.
- Select the
org.eclipse.equinox.launcher.win32.win32.x86
fragment. - In the editor, in the Operations part of the form, select the
delete
method. - Make the Navigator View from the server instance visible to the user.
- In the Invocation View select the Delete button.
- Note: The launcher fragment project was deleted from the server's workspace.