AusLUG12 presentation

Thanks to everyone who attended my session on Lotus Notes package customisation and the positive feedback I have received so far.

Don’t hesitate to drop me a line if you need to know more details on any of the topics covered.

Feel free to download the presentation from here. Most presentations should also be made available in the AusLUG community after the event.

Sametime: prevent contact list notification after directory change to LDAP

If you have followed IBM’s instructions on replacing the Domino Directory with an LDAP directory you might notice the user notification below after running the stnamechange command against the vpuserinfo.nsf:

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.

Preference: showExternalModificationDialog
Value: false

Migrate in-line styles to css with XPages editor

There is a nice little option/feature on the Style tab of the Properties view in the XPages editor. It allows for the export of style parameter that had previously been defined manually in the code, to be migrated into a css file and automatically applied to the selected control. I like that!
Style Migration

Truncated documents in server replica

This morning I was stumbling upon a very interesting issue in Lotus Notes/Domino that involved truncated documents on a server replica. This is an issue as the database on the server is the only one, besides a number of local replicas on laptops.

A bit of research on the web unveiled that Almar Diel has encountered a similar problem, which pointed me towards the right solution.

In order to get the full documents back onto the server replica I had to find the laptop that was holding the replica with the corrupt replication formula as this had to be cleared out as described in workaround option 2 of this IBM technote.

This will ensure that all documents replicated from now on would not be appearing as truncated documents anymore on the server. In order to fix the existing truncated documents though, I had to remove the documents from the server replica without leaving deletion stubs. This can easily be achieved in utilising Julian Robichaux’ stub-less delete function documented here. Clearing out the replication history of the local database and issuing a new replication did make the documents re-appearing on the server replica in there entirety.

Thanks to Almar and Julian for documenting your solutions!

Why Microsoft can’t stop Lotus Notes

While hunting for something completely unrelated, Google presented me with this analysis on CNNMoney dated back to 2004 1994 (Thanks Carl!). It’s an interesting read and some of the stuff could actually be highlighted again as part of the LotusKnows campaign.

And now that I got your attention I might actually share the search phrase I was typing in: “lotus policy change is clearing replication history -click”

I am having an issue here where a change in dynamic desktop settings is clearing out the replication history of local databases on laptop computers, enforcing them to run the ‘one time only – replication setup’ again. This is a bit of a problem as most of the Laptops are still connected via pretty old dial-up.
The desktop settings document got a new database link added to the list of databases to be created as new replicas on the user’s machine.

New database link

Has anyone had this behaviour before? Is there any workaround for that? Server and Client version are both 8.0.2.