Create the widget attachment file to call the feature's update site
The widget's extension.xml file will contain an install manifest installfeature snippet with a pointer to the update site and specifications on how to install or update the feature. You can simplify the process described here by using the Features and Plugins wizard in Notes®.

About this task

Perform these steps to create the widget's extension.xml attachment file that you will use to call the update site and provision the feature to users.

Note: The Start Configuring Widgets toolbar button contains a Features and Plugins option. This option launches a wizard sequence designed to simplify the process of creating a Notes client plug-in deployment widget. The wizard guides you through the widget definition and extension.xml creation process. For details, see "How do I configure a Features and Plugins deployment widget?" in Notes user help.

Following are some sample XML definitions:

Items in the top section of an extension.xml file are described.

This example points to the site.xml file in an NSF-based update site.

By default, only public update sites that do not require authentication are available for feature deployment using widgets. However, you can use accounts to configure access to update sites that require user authentication.

Provided that shared="true" is set in the install manifest of the widget's .XML, the plug-in is installed to Notes_install_dir\framework\shared\eclipse. If there is no write access to that directory, the plug-in is installed to Notes_install_dir\data\workspace\applications.

Note: You can obtain the sample extension.xml file used in this example; see the related information links.


Create the extension.xml file. Use the sample XML below as a guide.

Note: See the related information for details about the contents of an install manifest, available in the Provisioning manifest DTD topic in the Lotus® Expeditor wiki.

Sample XML

The items in bold are the fields you need to customize for your own feature.

<?xml version="1.0" encoding="UTF-8"?>

<webcontextConfiguration version="1.1">

<palleteItem id="" imageUrl=""


title="Comp XYZ Custom Plugin"








<installfeature description="Comp XYZ Custom Plugin" id="Test_Feature_ABX" name="Test Feature ABX">


<feature download-size="10" id="Test_Feature_ABX" match="perfect" shared="true" size="10" version="1.0"/>









Parent topic: Deploying client plug-ins with widgets and the widget catalog
Previous topic: Create an NSF-based update site and import the Eclipse updateSite content
Next topic: Preparing for using widgets in the Notes client

Related concepts
Widget catalog options and access
Understanding the Eclipse update site

Related tasks
Deploying client plug-ins with widgets and the widget catalog
Creating and using an NSF-based update site
Assigning NOTES.INI or location document settings using a desktop policy
Assigning Eclipse preference settings using a desktop policy

Related information
Provisioning manifest DTD
How to use a Notes widget to deploy a new plug-in to an existing Notes installation