I can not think of any valid reason why a user should be bothered that his ‘contact list has been updated to reflect recent administration changes to contact names’. In my experience it would just puzzle people, especially since there is no true information relayed or any action required.

Fortunately we have given the possibility to to suppress the prompt for the user either using a managed setting in the plugin_customization.ini or a desktop policy.

Plug-in: com.ibm.collaboration.realtime.imhub
Preference: showExternalModificationDialog
Value: false

While I wouldn’t necessary pronounce that it was worth the wait, while applying the workaround in Lotus Notes and Domino 6 to 8, it’s definitely a feature that has been waited for a long time.

In order to enable the Eclipse update manager UI in Lotus Notes:

1. Close you Lotus Notes client
2. Browse to the plugin_customization.ini in the notes application folder\framework\rcp
3. Add com.ibm.notes.branding/enable.update.ui=true
4. Save and close file and restart Lotus Notes

You can now find the Eclipse update manager under File > Application > Application Management.

Very little to nothing has been changed in the general procedure outlined below:

1. Installation of the IBM Lotus Sametime 7.5.1 SDK
2. Installation of Eclipse 3.2.2
3. Installation of the J9 Java Development Tools (JDT) for Eclipse
4. Configuration of the run time environment
5. Configuration of the target platform
6. Creation of the launch configuration

The Sametime 7.5.1 SDK has been linked before on this side. The installation is not different to the installation of the 7.5 SDK and it is not required to remove the previous version as long as the new software development kit will be placed into a different directory.

Lotus Sametime 7.5.1 is based on the Eclipse 3.2.2 Rich Client Platform (RCP). Therefore it is not required to have the 3.2 binaries available any more to overcome the compatibility issues described before. The Eclipse SDK can be downloaded from the Eclipse home page.

Nothing has changed in regards to the J9 JDT plug-in. Whereas the IBM provided link in the book has been discontinued. I am wondering how long my link to the current version might survive.

So far a lot hat has been common between the previous and the new version. The first major difference can be discovered while adding the J9 runtime environment. The three Java archives harmony_regex.jar, nio.jar and sound.jar have been moved to the same directory (jclMax) as the other libraries. The string library, which contained 3 string classes is not part of the packet any more.

The target platform will of course be the program directory of the Sametime Connect Client 7.5.1. Do not forget to add the Eclipse archives

org.eclipse.platform.source.win32,
org.eclipse.platform.source,
org.eclipse.rcp.source.win32 and
org.eclipse.rcp.source

as additional source code locations for the target development environment.

So far the final step would be the creation of the Sametime launch configuration. As far as I am aware nothing needs to be changed in here. So the arguments for the java application launcher in windows would still be

Xint -Xtrace:none -Xgcpolicy:gencon
-Djava.home=C:\st751sdk\client\connect\j9-runtime\win32
-Dcom.ibm.pvc.webcontainer.port=7777

Explaination to the Java launcher options can be found in the Java Development Kit (JDK) documentation.

The information provided in this article are based on the IBM Redbook Extending Sametime 7.5 – Building Plug-ins for Sametime while considering the amendments required to work with the most recent program versions as well as SDK.