Skip to main content
Jump to: navigation, search

Difference between revisions of "Equinox/p2/Getting Started"

< Equinox‎ | p2
(Step 2 - Exploring the agent)
(Step 2 - Exploring the agent)
Line 39: Line 39:
 
# Profiles - the '''Profiles''' view.
 
# Profiles - the '''Profiles''' view.
  
The Metadata Repositories view is empty, so first let's add a repository on eclipse.org which contains metadata for the Eclipse SDK, and other goodies.  (This may take awhile, we're working on the performance here)...
+
The Metadata Repositories view is empty, so first let's add a repository on eclipse.org which contains metadata for the Eclipse SDK, and other goodies.  You can do this from the popup menu in the Metadata Repositories view.
 +
 
 +
    [[Image:SelectAddRepository.jpg]]
 +
 
 +
 
 +
You'll see a dialog that lets you add a URL (or a local directory or jar file).  We're going to use a test update site on eclipse.org.  (This may take awhile, we're working on the performance here)...
  
 
     [[Image:AddMetadataRepo.jpg]]
 
     [[Image:AddMetadataRepo.jpg]]

Revision as of 12:40, 1 November 2007

Overview

What is the first thing that you would expect to do with some provisioning code - install something, of course! This section is to guide you through a happy-path using equinox provisioning to install an Eclipse SDK.

There are four basic concepts that will help you understand the install:

  • Agent - the program that will perform the install. In general, the provisioning agent could appear in various forms - a standalone application, a silent install demon, a perspective in the ide. We will use the Admin UI application to do our install.
  • Metadata - the information about what can be installed. The metadata is used by the agent to analyze dependencies and perform the installation steps. Metadata lives in one or more repositories.
  • Artifacts - the actual bits that will be installed. There are various kinds of artifacts that are processed differently during the install. Associated metadata determines how a given artifact is processed. Artifacts live in one or more repositories. The metadata and artifacts generally come from different repositories and may be widely distributed.
  • Profile - in the most simple form, a profile is the location where the bits will be installed. The term 'profile' is not a very good term and probably will disappear from end user concepts (there's a bug about this), but it is the term we are using for now.

Steps to using the agent

In this example, we will be installing a 3.4M1 SDK. The current agent only supports Windows but M2 should see us building and testing on a wider range of platforms.

Step 1 - Exploring the agent

The Admin agent application is available from the Equinox download site - click the link and you should see (Firefox)

   AgentDownload.jpg

The zip file is ~15 MB. Download it and unzip it anywhere on a writable local drive. The result of this step is that you will have a directory (equinox.prov) containing the agent:

   ProvDirectory.jpg

Step 2 - Exploring the agent

Double-click on the eclipse.exe and the Admin UI will come up. It looks something like (resized to fit here):

   InitialRCPAgent.jpg

Note that you see here all four concepts:

  1. Agent - the main window.
  2. Metadata - the exposed Metadata Repositories view.
  3. Artifacts - the hidden Artifact Repositories view.
  4. Profiles - the Profiles view.

The Metadata Repositories view is empty, so first let's add a repository on eclipse.org which contains metadata for the Eclipse SDK, and other goodies. You can do this from the popup menu in the Metadata Repositories view.

   SelectAddRepository.jpg


You'll see a dialog that lets you add a URL (or a local directory or jar file). We're going to use a test update site on eclipse.org. (This may take awhile, we're working on the performance here)...

   AddMetadataRepo.jpg

Once the repository has been added, you should see something like this:

   RCPAgent.jpg


The Profiles view shows the Equinox Provisioning UI profile which is profile defining the install location for the Admin UI app you are running. If you right click on the list item and select properties, you will see some information about this profile:

   AgentProfileProperties.jpg

If a Metadata repository or a Profile is not empty, then you can expand it to see the installable units (which are really installed units) in the profile. A preference is available to show only the installable units which are a Group; the default for this preference is true. Expanding to show the groups will give you something like this:

   ExpandedInstallableUnits.jpg

Switching to the Artifact Repository tab and expanding will show:

   Artifacts.jpg

Step 3 - Creating a new profile

You will need to decide where you want to install the SDK and create a profile for that location. In the profile view, right click and select 'Add a new profile':

   SelectNewProfile.jpg

then fill in the appropriate data in the Profile properties dialog:

   NewProfile.jpg

The meaning of the Flavor property is an advanced topic, so don't play with that unless you want to explore error conditions! In fact, once it has been set in a profile and something has been installed using that flavor, the Flavor property should be non-modifiable (bug).

Step 4 - Doing the install

The sdk group is near the bottom of the list of group installable units in the repository http://download.eclipse.org/eclipse/equinox/provisioning/servers/metadata/ so scroll down until sdk is in view. The Admin UI supports two ways of initiating an install: 1). you can right click on the sdk group, select Install..., then choose the profile in the resulting popup dialog; or 2). you can drag&drop the sdk group onto the profile. Let's do d&d since it is easier (the little smudge over MyEclipseSDK is the drop cursor):

   DropSDK.jpg

You will be prompted to give a name for the software being installed. This is really asking you to give a nickname to the software that will be meaningful for you.

   PromptName.jpg

Next you will be asked to confirm that you really want to go ahead with the install. Click Yes.

   ConfirmInstall.jpg

The install will start (assuming you have network connectivity org.eclipse.download, no firewall issues, etc):

   InstallProgress.jpg

Anecdotally, the install takes slightly less time than the download of a corresponding Eclipse SDK zip (one datapoint: 21 minutes for equinox provisioning install vs. 23 minutes for download of the zip).

Step 5- After the install

The install will finish with a whimper, not a bang, as the progress dialog disappears and the new profile you created is populated with the groups and installable units that are now installed into the profile:

   AgentPostInstall.jpg

The directory you chose for your profile location will look like this, before running the eclipse you just installed:

   InstalledSDK.jpg

Step 6- Installing the end user UI

The Agent UI is really intended for system administrators and power users who want to browse and manage the applications they have installed. A typical end user of an Eclipse-based application doesn't want to be exposed to all these concepts of metadata, artifacts, profiles, and IUs. They just want to install, run, and update their software. For this purpose, there is a p2-based end user UI intended for dropping into an Eclipse application. Once you have installed the SDK, you can install this end-user UI by dragging the "End User UI" group from the metadata repository into the profile that you just installed the SDK into. Now, when you start up the SDK, there will be a new menu entry (Help > Software Updates (Incubation), that you can use to manage and update the running application.

See also

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.

For more detailed information, visit one or more of the following pages:

Back to the top