Difference between revisions of "Equinox Resource Monitoring Demo"
|Line 38:||Line 38:|
the extension points are listed
* to the runtime.applicationsextension point
the server application and application
* :we hook in Tom's demos here? click on an extension and start it remotely?
Revision as of 11:51, 2 March 2007
Demo - in SDK
- 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
org.eclipse.equinox.*in the filter to get all the Equinox projects selected and choose Add
- 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.
- 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)
- Note: The Contributions View will be populated with the available contributions from the server.
- In the Contributions View, expand the Bundles element.
- Note: These are all the bundles that are installed on the server.
- 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.
org.eclipse.equinox.commonto show it is recursive.
- Expand Services.
- Note: there are 3 different icons, one each for providing, using, and both.
- In the Contribution View expand the Extension Points element.
- Note: All the extension points are listed.
- Navigate to the
- 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.
- Expand Preferences -> instance -> org.eclipse.core.resources
- select node
- select operation Put
- In Invocation view, make the key "description.autobuilding" and the value "false"
- Window -> Preferences -> General -> Workspace
- Note that the Build Automatically preference is now unchecked
- expand org.eclipse.core.runtime.IExtensionRegistry
- expand Bundles and see who is importing the service, exporting the service, and both
- expand Sleak
- TODO why don't these numbers look right??
- expand VM Stats
- look at all the VM info
- see the 6 equinox projects in the workspace.
- select the launcher fragment
- in the operations part of the form, select delete
- make the navigator from the server instance visible to the user
- in the invocation view hit Delete
- note that the resource was deleted from the server
Demo - standalone application
- unzip exported product
- set up ppro VM
- start the server
- get the osgi.jar from the latest build
- start OSGi: java -jar osgi.jar -console
- install the file installer jar
- drop in the server bundles