Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Equinox/p2/Admin UI Users Guide"

< Equinox‎ | p2
(For more information)
(About the Eclipse Provisioning RCP Agent)
Line 2: Line 2:
  
 
== About the Eclipse Provisioning RCP Agent ==
 
== About the Eclipse Provisioning RCP Agent ==
* If you have not yet downloaded the Eclipse Provisioning RCP agent, see [[Equinox Provisioning Getting Started#Getting Started with M1 | Getting started with M1]].  You will need to unzip the agent application into the root of your C:\ drive.  (This will get more flexible later).  Launch the eclipse.exe program located in c:\equinox.prov and you should see something like this:
+
* Once you've downloaded and unzipped the Eclipse Provisioning RCP agent, launch the eclipse.exe program located in c:\equinox.prov and you should see something like this:
 
[[Image:RCPAgent.jpg]]
 
[[Image:RCPAgent.jpg]]
* In general, the [[Equinox Provisioning Concepts | agent]] RCP application allows you to add, remove, and browse the provisioning repositories, and install and uninstall software into various [[Equinox Provisioning Concepts | profiles]].  It exercises the Equinox Provisioning framework.
+
* In general, the [[Equinox Provisioning Concepts | agent]] RCP application allows you to add, remove, and browse the provisioning repositories, and install, uninstall, and update the software in various [[Equinox Provisioning Concepts | profiles]].  It exercises the Equinox Provisioning framework.
* For M1, our goal is to demonstrate that you can use the agent to install (and uninstall) an Eclipse 3.3 SDK
+
* For M2, our goal is to use the agent to provision an Eclipse SDK and add the provisioning update UI, so that you can then run and update an Eclipse 3.3.x SDK
 
* The agent application itself is structured on top of the provisioning framework, so you can (purposefully or inadvertantly) modify the agent application by manipulating its profile within the application.
 
* The agent application itself is structured on top of the provisioning framework, so you can (purposefully or inadvertantly) modify the agent application by manipulating its profile within the application.
* The UI for the RCP app is simply a browsing interface into the provisioning API.  It does not represent what we think actual user workflows for installing or updating an Eclipse-based application would be.  We'll focus on that later on.  In other words, it is not intended to replace the Eclipse Update Manager UI.  For background, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=197405 Bug 197405)
+
* The UI for the RCP app is simply a browsing interface into the provisioning API.  It does not represent what we think actual user workflows for installing or updating an Eclipse-based application would be.   
 
* The workflow we are trying to demonstrate is very narrow, yet the UI is more flexible in manipulating the environment.  Failures are brittle (vague error reporting that requires you to check your .log file).
 
* The workflow we are trying to demonstrate is very narrow, yet the UI is more flexible in manipulating the environment.  Failures are brittle (vague error reporting that requires you to check your .log file).
 
* The UI described below can also be run from a full Eclipse SDK workbench.  You can open the '''Provisioning''' perspective to see the same functionality.
 
* The UI described below can also be run from a full Eclipse SDK workbench.  You can open the '''Provisioning''' perspective to see the same functionality.

Revision as of 23:40, 20 September 2007

About the Eclipse Provisioning RCP Agent

  • Once you've downloaded and unzipped the Eclipse Provisioning RCP agent, launch the eclipse.exe program located in c:\equinox.prov and you should see something like this:

RCPAgent.jpg

  • In general, the agent RCP application allows you to add, remove, and browse the provisioning repositories, and install, uninstall, and update the software in various profiles. It exercises the Equinox Provisioning framework.
  • For M2, our goal is to use the agent to provision an Eclipse SDK and add the provisioning update UI, so that you can then run and update an Eclipse 3.3.x SDK
  • The agent application itself is structured on top of the provisioning framework, so you can (purposefully or inadvertantly) modify the agent application by manipulating its profile within the application.
  • The UI for the RCP app is simply a browsing interface into the provisioning API. It does not represent what we think actual user workflows for installing or updating an Eclipse-based application would be.
  • The workflow we are trying to demonstrate is very narrow, yet the UI is more flexible in manipulating the environment. Failures are brittle (vague error reporting that requires you to check your .log file).
  • The UI described below can also be run from a full Eclipse SDK workbench. You can open the Provisioning perspective to see the same functionality.

Overview of the Eclipse Provisioning RCP Agent

  • The RCP app is comprised of three views:
    • The Metadata Repositories view shows those metadata repositories known by the provisioning infrastructure.
      Metadatarepo.jpg
      • You can (and should) ignore those repositories located in your c:/equinox.prov directory. Those are the repositories containing the RCP agent application.
      • The repository of interest is the repository located on eclipse.org (http://download.eclipse.org/eclipse/equinox/provisioning/metadata/).
      • You may add or remove repositories using this view.
      • Expanding a metadata repository will show you the installable units(IU's) available for installing.
      • You may examine the properties of repositories or IU's
      • You may install an IU to a specified profile using drag and drop or the popup menu.
    • The Artifact Repositories view shows those artifact repositories known by the provisioning infrastructure.
      ArtifactRepo.jpg
      • You can (and should) ignore those repositories located in your c:/equinox.prov directory. Those are the repositories containing the RCP agent application.
      • The repository of interest is the repository located on eclipse.org (http://download.eclipse.org/eclipse/equinox/provisioning/artifacts/artifacts.xml).
      • You may add or remove repositories using this view.
      • Expanding an artifact repository will show you what artifacts are located there
      • You may examine the properties of the repository
      • You can't examine the properties of the artifacts or otherwise manipulate them (yet)
    • The Profiles view shows profiles defined for installing software. Profiles are the target of an install operation.
      Profiles.jpg
      • The EquinoxProvisioningUI profile represents the agent application itself. It contains the IU's (bundles) that comprise the RCP app.
      • You may add or remove profiles using this view.
      • Expanding a profile shows you what IU's have been installed in the profile.
      • You may examine and change the properties of profiles and IU's.
      • You may uninstall an IU from a profile using the popup menu.
  • The Window>Preferences... menu item lets you control some application preferences:
    • You can control whether drag and drop operations should be confirmed first
    • You can control whether you view all IU's in the repositories and profiles, or just those that have been marked as a "group" IU. Viewing only the groups helps to reduce the clutter when you are trying to find something like the SDK.

Installing the Eclipse 3.3 SDK using the Provisioning RCP Agent

  • Define a profile representing your Eclipse SDK install
    • From the profile view's local menu, toolbar, or popup menu, choose Add Profile...
      NewProfile.jpg
    • Choose a unique id for your profile, such as "Eclipse SDK".
    • You may optionally define a name and description to further describe your profile
    • Choose an install folder for the profile (this is where the SDK will be installed).
    • It is important to keep the defaults for the other values, or the install may fail with little explanation
    • When you have pressed OK you should see the new profile in the view
  • Locate the sdk IU in the eclipse metadata repository
    SDKInMetaRepo.jpg
  • You may install the sdk in several ways by selecting the IU and dragging it to your newly created profile. You can also select the IU and choose Install... from the popup menu. You will be prompted for a target profile.
  • You should see a progress indicator that reports the progress of the install. In some phases, progress reporting is very sparse. You may see some long pauses without progress.
  • When it is finished, you have a full Eclipse SDK located in the install folder of your profile.

Running the Admin UI from Eclipse

You can run a full-featured version of the provisioning admin UI from an Eclipse SDK Workbench. Equinox Provisioning Getting Started for Developers explains how to set up your Eclipse environment to run the provisioning code. Some additional function is available when running the UI from an SDK:

  • Undo support is available from the Edit menu when working in the various views. The undo support is not (yet) using rollback or operation history kept by the provisioning infrastructure. It is implemented at the UI level (undo of an install performs an uninstall, undo of an add performs a remove, etc.)

Cool stuff you can try

  • If you install the SDK into the agent profile (EquinoxProvisioningUI), then the next time you launch the rcp app, you'll actually be running the Eclipse SDK with the Provisioning Perspective.

For more information

If you encounter bugs, or would like to enter enhancement requests for this work, please use the Equinox Incubator category in Bugzilla. You can add the prefix "[prov]" to the subject line of the bug report to help us with bug triage.

Back to the top