This process is written as an ordered procedure and assumes you have a valid Eclipse update site containing a features folder, plugins folder, and site.xml file and that all JAR files in the update site folders are properly signed. It also assumes you want to deploy this plug-in to an existing user such that it be installed, and that any updates to it be automatically provisioned, for that user.

Note Once you have performed these steps, users will be automatically provisioned with the feature called by the widget's extension.xml. The feature called by the widget you are about to create will be installed when the user's local widgets catalog is updated. As well, any updates you make to the feature will be provisioned to the user by way of the widget. The client checks the widget catalog for updates periodically and upon user request.

Note This procedure parallels one documented for an earlier release in Lotus Tech Note 1305829 at http://www.ibm.com/support/docview.wss?rs=899&uid=swg21305829.

You will use these items to complete the process:

• Widgets catalog on named Domino server
• Correctly configured Widgets section of Domino Desktop policy settings document
• Correctly formed and signed Eclipse update site containing the feature(s) to deploy
• NSF-based update site containing your Eclipse update site
• Widget resident in the widgets catalog and of the same category as the user's policy or preference
• Correctly formed widget XML file attachment that calls the update site

  Note: Two sample extension.xml files are attached to Lotus Tech Note 1305829.

The main steps for deploying a new feature using a widget are as below:

• Place the feature's valid Eclipse update site, containing the signed features and plug-ins, in a central location
• Install or upgrade the server and client, create the widgets catalog, and set widgets policy or preferences
• Create an NSF-based update site and import the Eclipse update site
• Create the extension.xml that the widget will use to call the feature's update site
• Display the Widgets sidebar and verify or set catalog access
• Create the widget in the widgets catalog and attach its extension.xml file to call the update site
• Test the widget by dragging it from the catalog view to your My Widgets sidebar
• Communicate to users how to obtain the widget or inform them that they will be automatically provisioned with the widget and its feature

• Notes My Widgets overview
• Catalog options and access
• Format of the Eclipse update site
• Specifying available update sites
• Controlling feature install and update with update sites
• Controlling My Widgets access with Eclipse preferences

Related topics

Using a widget to deploy a client plug-in
Place the feature's valid Eclipse update site, containing the signed features and plugins, in a central location
Install or upgrade the Domino server and Notes client, create the widgets catalog, and set widgets policy or preferences
Create an NSF-based update site and import the Eclipse update site
Create the extension.xml that the widget will use to call the feature's update site
Display the Widgets sidebar and verify or set catalog access
Test the widget by dragging it from the catalog view to your My Widgets sidebar
Communicate to users how to obtain the widget or inform them that they will be automatically provisioned with the widget and its feature
Managing client plug-in deployment
Understanding Widgets and Live Text user types
Catalog options and access
Creating the widget catalog
Creating a client management widget in the widget catalog

Glossary