Configuring the widget catalog application

The widget catalog is a server-based application that contains all centrally managed widgets and their underlying XML extension definitions, including content types and recognizers. The catalog is based on the IBM® Domino® server-supplied Widget Catalog template, toolbox.ntf, and its access is controlled by a combination of application ACLs and policies or Eclipse preferences in the plugin_customization.ini file, as well as widget catalog categories. Use the supplied catalog template, toolbox.ntf, to create a widgets catalog on a server. To configure the widget catalog application, configure ACLs and roles, enable agents, and (optional) set launch options for the widget catalog.

After you create the widget catalog, you have the option of creating an initial set of categories for the catalog. There are two types of predefined categories in the widget catalog; both can be defined in the Administration/Keyword view.
Table 1. Predefined category types in widget catalogs
Category Type Description
Administrator categories Named ADMIN-Categories. Only administrators can put widgets in these categories.
Categories Any widget author can add a widget to these categories.
You can use the desktop settings policy document or plugin_customization.ini file preferences to assign user access to the categories.

You (and experienced users with appropriate access) can configure new widgets and publish them to the catalog for user access. Users obtain the latest widgets from the catalog on a scheduled basis. Depending on how users are configured they can browse the catalog for new widgets and update the widgets in their local catalog replica on demand.

The widgets catalog does not contain IBM-supplied widgets. However, it does contain some advanced recognizers, and their content types, such as the following:
Note: These Live Text recognizers are available for American English-only and some German names. You can create your own Live Text recognizers using Java™ regular expressions.

The widgets that a user sees in the sidebar, and actions that are available to users based on category provisioning from the catalog, are stored in the local replica of the central catalog application.