Lotus Domino Administrator 8.5 Help - Create the extension.xml that the widget will use to call the feature's update site

NOTES CLIENT INSTALLATION AND UPGRADE

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

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.

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

Information about the contents of an install manifest and specifically the <installfeature> section is available in the "Provisioning manifest DTD" topic in the Expeditor Client for Desktop and Devices, Version guide in the Expeditor information center at http://publib.boulder.ibm.com/infocenter/ledoc/v6r11/topic/com.ibm.rcp.tools.doc.admin/manifestDTD.html.

Sample XML:

The items in

bold

are the fields you need to customize for your own feature.

Note You can obtain the sample extension.xml file used in this example from Lotus Tech Note 130582 at http://www.ibm.com/support/docview.wss?rs=899&uid=swg21305829.

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

<webcontextConfiguration version="1.1">

<palleteItem id="com.mycompany.xyz.extensions.featureABX" imageUrl=""

providerId="com.ibm.rcp.toolbox.prov.provider.ToolboxProvisioning"

title="Comp XYZ Custom Plugin"

url="nrpc://WidgetCatalogServer.abx.com/updatesite.nsf/site.xml">

<preferences>

</preferences>

<data>

<installManifest>

<![CDATA[

<install>

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

<requirements>

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

</requirements>

</installfeature>

</install>

]]>

</installManifest>

</data>

</palleteItem>

</webcontextConfiguration>

Sample XML definitions:

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

xml version = internal setting, use exactly as specified in the sample
encoding = internal setting, use exactly as specified in the sample
webcontextConfiguration version = internal setting, use exactly as specified in the sample
palleteItem id = internal ID setting, this must adhere to the namespace/ID format as specified in the sample - this value must be unique for each pallette item
imageURL = URL at which the widget graphic that appears in the My Widgets sidebar resides, if no value is specified a default graphic is used
providerID = states the widget's intent, for widgets that deploy features you must use exactly as specified in the sample
title = widget name that appears in the My Widgets sidebar panel
url = pointer by which the update site and site.xml are located. You can specify a URL value using NRCP protocol if the update site resides in an NSF-based update site (for example, updateSite.nsf) on a Domino server or using an HTTP protocol if the update site exists on an HTTP server.

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

Note 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.

Items in the <installManifest> section of the sample XML file are described in the "Provisioning Manifest DTD" link at the top of this section.

Catalog options and access

Understanding the Eclipse update site

Creating and using an NSF-based update site

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary