Created: Monday, 15 June 2009
Created: Monday, 15 June 2009
Created: Sunday, 24 May 2009
Based on several years of experience evaluating custom Notes applications to diagnose performance-related issues, IBM compiled the most common properties that can affect application performance. On two websites they cover the database, view, and form properties known to affect application performance. They will tell you when to use and when not to use certain properties for best performance results, and where applicable, IBM will provide you with alternative solutions.
This article looks at the database, view, and form properties that most commonly affect how well your applications perform.
This article looks at coding practices that can improve application performance. It also examines some common LotusScript methods to see which ones perform best under different conditions.
These articles aren´t brand new ones. But they include some good points for application performance.
Created: Tuesday, 19 May 2009
In Lotus Domino, the Event Correlation cache is used as a holding area in which Domino Domain Monitoring (DDM) events are correlated to previously encountered events. When this cache grows to its maximum size, the server reports the following error:
2009-01-27 23:04:29 Event: Error adding event document to Domino Domain Monitoring: Event correlation cache is full. You can increase its size via the NOTES.INI setting EVENT_CORRELATION_POOL_SIZE.
Maybe you tried to change the EVENT_CORRELATION_POOL_SIZE notes.ini variable, but that doesn´t solve your problem. Even with the maximum configured pool size from 100MB (EVENT_CORRELATION_POOL_SIZE=104857600), you may still see the above error. This occurs because Domino creates cached documents that are 2MB in size and the server allows a maximum of 200 cached documents by default.
Since 2MB x 200 is greater than the maximum allowable pool size, the error can occur unless additional parameters are enacted to control the document size and/or the maximum number of cached documents. The following notes.ini parameters are available for these purposes.
- DDM_MAX_NOTE_CACHE (number of documents in the cache)
- DDM_MAX_DOCSIZE_MB (size in megabytes of documents in the cache)
To finetune these values you need to check your ddm.nsf. The best way is to create a new view which lists all documents and enter a new column which show the size from the documents. The biggest document in this view can be used to finetune the DDM_MAX_DOCSIZE_MB value. In my example the biggest document is a 712KB big document (a event which is 2 years old but reopen from time to time), all the other documents are smaller (+-250KB).
To ensure now that the Event Correlation cache will not be exhausted when configured to the maximum 100MB size, I use these information and the parameters from above so that the following formula is true:
- DDM_MAX_NOTE_CACHE x DDM_MAX_DOCSIZE_MB <= 100
After you set these values (via set config ... on the console) you need to restart the events task.
Created: Thursday, 14 May 2009
Announcement Letter Number 309-533
May 12, 2009
For a limited time only, the commercial Passport Advantage® Relationship Suggested Volume Prices (RSVP) and Passport Advantage Express™ Suggested Retail Price (SRP) for selected eligible IBM® Lotus Notes® products have been reduced by 25%.
The reduction also applies to Passport Advantage Agreements with an Attachment for an Academic Volume Option.
Start and/or end dates
Orders must be received by IBM on or after May 12, 2009, but no later than August 5, 2009. Software entitlement (date of purchase) must occur on or after May 12, 2009, but no later than August 5, 2009.
Created: Thursday, 30 April 2009
A customer called me today. He re-certified all server and users and asked if there is a way to rename the old servernames into the new ones in bookmark.nsf and desktop6.ndk.
You could use the DSKTOOL.EXE for this. But it must be placed on every workstation on every notes programm directory (and must be started with some DOS commands).
After a look on the environment from the customer I found a quick and easy way. He placed the notes datafolder on a network share (sure this isn´t supported, but it works) and with a small script I was able to remove all old servernames he had in the past and was also able to rename all server names with one batch script. The script created also a backup from bookmark.nsf and desktop6.ndk on the same drive (via 7za command line option).
All what I need for this script was a installed Lotus Notes Client and access to the root from the networkshared (mapped as drive Z) for there notes user. The script took 5 hours to update all 2.000 .
Click on read more to see the script.
The file dskfile.txt in the script define which server should be removed or renamed. See the help for the DSKTOOL.EXE for more informations.