Complete guide to manually uninstalling “plugins” from Lotus Notes

As you probably know installing and uninstalling Java extensions (“plugins”) into the Lotus Notes client is easy using either File >> Application >> Install, File >> Application >> Application Management or the widget catalog. Sometimes however this doesn’t work and you’ll have to resort to a manual uninstall. This blog post outlines the way to perform a manual uninstall.

We have to start with some basics though. A Java extension in Lotus Notes (also known as a “plugin”) consists of two things:

  1. Eclipse plugin(s)
    The plugin is where the actual code and functionality is stored together with additional resources such as images, string translation etc.
  2. Eclipse feature
    The feature is what’s actually installed from a Lotus Notes perspective. The feature points to the Eclipse plugins that provides the actual functionality. It’s almso important to note that a single feature may reference multiple plugins.

Both an Eclipse plugin and an Eclipse feature are represented in the file system as JAR-files (files with an extension of “JAR”) and both of them are kept in the file system. A JAR-file is just a fancy ZIP-file with a predefined folder structure. Eclipse Features and plugins are stored in two directories beneath your Notes data directory (<Notes data dir.>/workspace/applications/eclipse/features for the features and <Notes data dir.>/workspace/applications/eclipse/plugins for the plugins).

From the above it may seem obvious that simply deleting these files will uninstall a Java extension – unfortunately there’s a final piece to the puzzle. Lotus Notes also keeps a record of what’s installed in a file called platform.xml (stored in <Notes data dir>workspace.configorg.eclipse.update). Simply deleting the feature(s) and plugin(s) may seem to work but will misbehave for instance when activating the File >> Application >> Application Management interface. The solution is to edit this file as well.

The complete steps to manually uninstalling a Java extension is therefore as follows:

  1. Close Lotus Notes
  2. Open the “features”-directory (<Notes data dir>workspaceapplicationseclipsefeatures)
  3. Locate the Eclipse features to uninstall.
  4. For each Eclipse feature you need to open it and edit the feature.xml file. Locate the <plugin>-tags and fine the names of the referenced plugins. Note that there might be more than one. Combining the plugin id and the plugin version will give the full filename of the plugin (<plugin id>_<plugin version>.jar).
  5. Delete the Eclipse features you’re uninstalling.
  6. Open the “plugins”-directory (<Notes data dir>workspaceapplicationseclipseplugins).
  7. Delete the plugin JAR-file(s) you recorded in the step above.
  8. Open the directory containing the platform.xml file (<Notes data dir>workspace.configorg.eclipse.update).
  9. Edit platform.xml and go to the end of the file.
  10. Remove each entry you see for the features you deleted in the step above.
  11. Save and close the file.
  12. Since Lotus Notes also keeps a record of which Java extensions to load it’s best to start Notes with some parameters to make it recompute the Java extension registry: notes.exe -RPARAMS -clean

Let me know if the above doesn’t work for you.

Please note: Manually uninstalling a Java extension installed via a widget descriptor via a widget catalog/policy will probably just make it reinstall once uninstalled.

12 thoughts on “Complete guide to manually uninstalling “plugins” from Lotus Notes”

  1. When you do it the other way around, does it mean you can install plugin doing this steps? Tried today, looks like I did all of them and it still doesn’t want to work (the other machine is controlled by policy :(()


  2. It should be possible to copy the plugin jar-files into the workspace plugin directory (notes binary/data/workspace/applications/eclipse/plugins) and restart the client using -clean (notes.exe -RPARAMS -clean) to make sure the plugin dependencies are rescanned. Should work as this was how we installed plugins into Notes way back… 🙂

    Let me know if it does.


  3. 😦 tried to copy the jar file with no success. We do something wrong or it doesn’t work because of some policy settings 😦


  4. thanks its a very good article. Our experience was versioning  through policy did not went good. Even though we gave a new category name , new version number ,feature ID for feature and plugin’s … and reapplied the policy which has new category name. It did not update some users. Those users were still having the old widget on their screen , even though the widgetcatalog got replicated with the new one. Any idea how to deal with these situations?



  5. Mikkel – I love you and I want to have your babies

    plain and simple

    the <span style="font-family: ‘Trebuchet MS’, ‘Lucida Grande’, Tahoma, Verdana, Arial, sans-serif; font-size: 13.142857551574707px; line-height: 10.857142448425293px; ">notes.exe -RPARAMS -clean install was the key to removing the old file and allowing the new one to install – Icannot telly ou how mucgh I hate installing plugins with eclipse and maybe maybe mAAAAYBE now this might be a little better in the future</span> 




  6. Worked for me when un-installing the Linked-In plugin.

    LinkedIn announced they’re no longer supporting the plugin, but neglected to create instructions for un-installing. 


Comments are closed.