Developing plugins for IBM Notes on Mac

I’ve been developing plugins for IBM Notes on Mac for years now but never really got around to sharing the steps on the blog. The below steps – in very crude form – works with Java 8 on Mac OS El Capitan (v. 10.11) using IBM Notes 9.0.1. The below sections are additions to the regular steps on creating a target platform documented otherwise on this blog

Main-tab

Run a product: com.ibm.notes.branding.notes

Execution Envionment: JavaSE-1.6

Arguments-tab

Program arguments:

-personality com.ibm.rcp.platform.personality
-debug
-console
-ws cocoa

VM Arguments:

-Declipse.registry.nulltoken=true
-Djava.util.logging.config.class=com.ibm.rcp.core.internal.logger.boot.LoggerConfig
-Dcom.ibm.pvc.webcontainer.port=8080
-Declipse.pluginCustomization="/Applications/IBM Notes.app/Contents/MacOS/rcp/plugin_customization.ini"
-Djava.protocol.handler.pkgs=com.ibm.net.ssl.www.protocol
-Dosgi.hook.configurators.exclude=org.eclipse.core.runtime.internal.adaptor.EclipseLogHook
-Dosgi.framework.extensions=com.ibm.rcp.core.logger.frameworkhook
-Xbootclasspath/a:"/Applications/IBM Notes.app/Contents/MacOS/rcp/eclipse/plugins/com.ibm.rcp.base_${rcp.base_version}/rcpbootcp.jar"
-XstartOnFirstThread

Environment-tab

  • DYLD_LIBRARY_PATH=/Applications/IBM Notes.app/Contents/MacOS
  • NOTESBIN=/Applications/IBM Notes.app/Contents/MacOS

Bob Balfe: plugin_customization.ini and Eclipse preferences

Bob has, once again, written a very nice post on his blog. This time it’s on plugin preferences and how the plugin_customization.ini file fits in and where Eclipse preferences are stored. As this is common cause of concern and questions from plugin developers and admins I wanted to point to the post.

Bob Balfe: plugin_customization.ini and Eclipse preferences

I’m on The Taking Notes Podcast episode 122

On Friday Bruce and Julian let me on The Taking Notes podcast to talk about plug-in development and how to get started with plug-in development. We also talked a bit about the RedWiki we’re writing. I think it’s a pretty decent discussion about the topic and I hope it’s a pleasant listen.

“Let’s talk Eclipse plugins! It’s not just an Eclipse thing, plugins can be used to extend the functionality of your Lotus Notes client.

Mikkel Heisterberg has been instrumental in helping developers wade through the murky waters of Lotus Notes sidebar app and plugin development for several years, through Lotusphere and user group presentations, blog articles, and onsite training. Bruce and Julian talked to him about how this plugin technology can be used and what’s going to be in the new IBM Redbook he’s been working on.”

The podcast may be found in iTunes or directly using the following link: Taking Notes Episode 122: 2010.09.24 – Sidebar, Plugins, and Notes Client Extensions with Mikkel Heisterberg

Option to install a widget from a .zip file, file structure, and focus on provisioning

Disclaimer: The following is from the release notes of Notes 8.5.2 so I don’t take credit for writing this. Lotus Notes 8.5.2 is in beta and there are no guarantees that the features described here will be in the final product that IBM ships.

Notes users can now install a widget that is supplied to them as a .zip file. Users can either drag and drop the .zip file into their My Widgets sidebar panel or use the Import menu option from the My Widgets sidebar panel.

This option is available for all supported widget types and enables the user to install a widget while working online or offline. The widget definition xml-file must be at the root of the zip file and the widget definition file name must be extension.xml. To make provisioning widgets self-contained in the .zip file, the updateSite URL in the widget definition must be set to jar:${zip.root}!/ and the updateSite itself must also reside in the .zip file.

The structure of the .zip file must be as follows:

features (DIR)
plugins (DIR)
extension.xml
site.xml

When a provisioning widget’s .xml definition is processed, the updateSite URL is replaced with a URL to the embedded updateSite in the .zip file. Automatic update is not supported.

Send/SMS… Sametime plugin

Using a couple of developerWorks articles (Extending the Lotus Sametime client with an LDAP directory lookup plug-in and Extending IBM Lotus Sametime Connect V7.5 with an SMS messaging plug-in) for inspiration I wrote a SMS plugin for the embedded Lotus Sametime client in Lotus Notes. The action goes in the Send menu when right-clicking a contact.

The plugin picks up the cellphone number from Domino Directory, supports sending to multiple contacts in one go and uses our exiting SMS gateway for sending the SMS’es (via e-mail). The hardest part was finding the menu path to use to stick the action where I wanted it. For others you should use com.ibm.collaboration.realtime.imhub.send/slotX where slotX is either slot1, slot2 or slot3 depending on where in the Send menu you want the action.

Once I’ve made it configurable which server to use for Domino Directory and how the SMS should be sent (which domain) I’ll probably make it publicly available.

Further reading

BAT-files (yup – you heard right!) to sign an entire update site

Digitally signing an Eclipse update after the fact (i.e. it’s not part of the build) can be tedious and time consuming. To make the process easier I wrote two small BAT-files that does the recursive signing of all plugin and feature JAR-files for you. Just stick the two BAT-files (signall.bat and dosign.bat) in the root Eclipse update site directory (together with site.xml) and invoke signall.bat.

Syntax
signall.bat <keystore path> <keystore password> <certificate alias from keystore>

Example
signall.bat mykeystore changeit signer_key

signall.bat

@echo off
set jdkhome=%JAVA_HOME%
for /f %%a IN ('dir /b /s *.jar') do call dosign.bat %1 %2 %3 %%a
set jdkhome=

dosign.bat

@echo off
echo Signing: %4
%jdkhome%binjarsigner.exe -keystore %1 -storepass %2 %4 %3

Java class line numbers for plugin developers

If you’ve been tasked with developing and/or debugging Java extensions for the Notes 8 client you know that line numbers has been missing from the stacktraces produced by Notes. This can be a real problem when trying to debug stuff in a production client. There has been some discussion among the ones of us developing these extensions on how to enable these line numbers. The other day this information was provided by Srinivas Rao of IBM and I wanted to publish it here for all to read.

Line numbers are removed from the classes added to the shared class cache to reduce the memory needed for the memory mapped classes. To re-enable the line numbers, one needs to edit the <notes>frameworkrcpdeployjvm.properties file and add comment out the ignorelinenumbers vm argument. However, if the classes have already been added to the JVM shared class cache, then they will have been added without line numbers. Either comment out the shared class cache (which will dramatically affect performance at startup) for temporary work, or shutdown notes and remove the shared class cache so that it can be repopulated with classes with line numbers. Of course, this will also affect the startup performance, but not so much as not having a cache

These are two of the key lines … to comment them out, add a # to the front of the line

vmarg.Xnolinenumbers=-Xnolinenumbers
vmarg.Dshare=-Xshareclasses:name=xpdplat_.jvm, **line cont**
   controlDir=${prop.jvm.shareclasses.loc}, **line cont**
   groupAccess,keep,singleJVM,nonfatal
jvm.shareclasses.loc=${rcp.data}/.config/org.eclipse.osgi

The shared class cache is typically located in the data/workspace/.config/org.eclipse.osgi