- Check the rich client log, available via Help - Support - View Trace. Enable trace logging for the widgets and provisioning subsystems to find out what is happening.
- Look at the features and plugins that have been installed in the user’s install site:
- Check the platform.xml file to see which features are enabled. Only installed and enabled features are recognized at runtime.
Hunter's ISSL Blog
HunterMedney 1100009YKB Marcações:  provisioning notes8 troubleshooting widgets 1 Comentário 7.839 Visualizações
Below are areas to look at when troubleshooting install/update/removal of Eclipse features and plugins via widgets.
HunterMedney 1100009YKB Marcações:  debugging notes notes8 troubleshooting logging expeditor 17.305 Visualizações
When deploying plugins using widgets in Lotus Notes 8 Standard, you may have need to see what’s happening under-the-covers.
Lotus Expeditor (Eclipse-based middleware on which Lotus Notes 8 Standard is based) funnels all logging through JSR 47 logging (java.util.logging). JSR 47 logging uses a configuration file to configure output and to set levels for each of the loggers.
When running Lotus Notes 8 normally (outside an IDE), the log configuration file is in:
rcpinstall.properties configures a number of settings for the platform and also doubles as the configuration file for JSR 47 logging. To enable trace logging for a given plugin or subsystem, set the level of the named logger for that plugin or subsystem in rcpinstall.properties. Logger names typically follow class/package names which typically follow plugin IDs.
The task of installing a plugin via a widget involves both the widget framework and the provisioning engine. To enable full trace logging for both of these sub-systems, append the following to rcpinstall.properties:
The next time Notes is started, the trace log will be full of entries related to provisioning and widgets.