Creating and using an NSF-based update site

Import Local Update Site

Use this action to import the contents of a local Eclipse update site, containing a complete features subdirectory, plugins subdirectory, and site.xml file into the active NSF-based update site.

Navigate to the update site's site.xml file as prompted.

You can import one or more Eclipse update sites into a single, consolidated NSF-based update site. For example, if you have three separate Eclipse update sites, you do not need to create three individual NSF-based update sites.

Import Features

Use this action to import individual features into the NSF-based update site instead of importing a complete Eclipse update site. There are two typical scenarios for using this action:

• A developer creates new features. Instead of exporting an entire update site, the developer exports only the particular feature he's working on and imports those features into the NSF-based update site. In this scenario case, the NSF-based update site would only contain that particular feature (and whatever plug-ins are associated with that particular feature).
• An administrator who previously imported a complete Eclipse update site (using the Import Local Update Site action), later receives updated features. The administrator can then import these individual features into his existing, and already populated, NSF-based update site. If the features he imports already exist, the features are either updated in the database (if the feature name and version is the same) or added as a new feature (if the feature name and version is different or doesn't yet exist).

Import Database

Use this action to import an existing NSF-based update site into the active NSF-based update site. This is similar to importing Eclipse update sites, except that the contents are imported from an existing NSF-based update site. For example, an administrator may have an existing NSF-based update site (for example, updatesite.nsf). A developer may provide him with another (probably smaller) NSF-based update site (for example, UPDATESITEABX.NSF). The administrator can import the entire NSF-based update site into his active NSF-based update site, effectively merging the content of both into a single NSF-based update site.

Update URL references

This action is available in NSF-based update sites that contain features and plug-ins.

Use this action to specify that Eclipse features and plug-ins are updated from the active NSF-based update site. Imported features and plug-ins may contain a specified update site URL, from which updates are to be obtained. As an administrator, you can determine that updates come from your NSF-based update site, rather than a source URL that may, for example, be outside your organization's control. You can specify an NSF-based update site as the site from which to obtain updates. Specify the URL of the Domino® server hosting the active NSF-based update site. Example syntax is provided in the dialog box.

New site label -- Type a name to label the local site URL, for example, ABXLocal site.

New site URL -- When you click the button next to this field, the Select URL dialog appears displaying the active update site URL in both HTTP and NRPC format. Click either the HTTP or NRPC option to pass that value to the New Site URL field.

Apply to Update site URL -- Pass the URL value as an update site value.

Apply to Discovery site URL -- Pass the URL value as a discovery site value.

Change features with embedded URL only -- Apply this new default update site value only to features that already have a default update site specified to overwrite that site value with this one.

Change ALL features -- Apply this new default update site value to every feature in the active Notes® application.

Note that this setting is similar to the site.xml specification found in an Eclipse feature's accompanying feature.xml file. Also note that the site.xml settings you specify here are overridden by settings that may exist in the Domino® server Configuration Settings document. For example, if the server Configuration Settings document has defined an update site list and specified that updates can only come from that site list (this is also called a whitelist) then the site you specify in this field must also exist in that whitelist or it will not be considered during an update request.

You can also obtain the New Site URL default value using the Action -- Show URLs menu sequence.