I’m sure many of you have written applications that involve full-text indexes, and found that the index doesn’t update for some time after your agent completes, even when the index frequency is set to ‘Immediate’. The Admin help suggests that such indexes are updated as soon as possible after the database is closed, but in fact, “as soon as possible” is not less than 15 minutes.
The request goes on a queue, and waits, so if the database is quite active, the index is updated every so often rather than after every change — reducing server loadings, but potentially increasing user irritation. In fact for some applications the can be quite a nuisance — especially, as in my case, you have a team of testers eagerly trying to break the application and being frustrated at the indexer delays. In the end they raised a trouble ticket and we had to respond It’s worth noting that the server behaviour differs from client behaviour — the client updates “Immediate” FTI’s directly as the database is closed.
Read more…
Viewed 6095 times by 1628 viewers
At some point during the day to day work, every network administrator and end user will inevitably come to the realization that even the media via e-mail has a darker side. Those who still have only ever tested positive aspects of the electronic messages generally look at the world through different eyes and are more prone to reckless behavior from a business standpoint.
Of course, there is no denying the benefits of e-mail as a means of communication – it reduces the communication channels, and serves as a cost-effective means to simplify and develop a range of business processes, from customer requirements through the initiation of contracts up to send an order confirmation. Against these advantages however, the legal obligations and safety-related problems that could become a serious headache for those businessmen who have decided to bury its head in the sand.
Read more…
Viewed 7873 times by 2117 viewers
Log file in lotus notes purging is generally managed by the “Log=” parameter in Notes.ini on Domino Server.
According to the .ini reference, the format for the “Log=” parameter is:
Log=logfilename,logoption,0,days,size,days2(optional)
|
The fourth parameter, “days”, is what’s important here. Most often, you’ll see that set to 7, for 7 days. Sometimes, you’ll see it set to 30. But either way, you shouldn’t have more than about 30 days in your log.nsf file.
So, the first thing to do is check your Notes.ini and see if somehow that parameter is inflated, for example, if it says something like 365 or even 20000. If so, then your log isn’t being purged because Notes has been told not to purge it.
Read more…
Viewed 7988 times by 2172 viewers
The following are some tips for making applications/views that perform well even with reader access controlled documents:
- Embedded view using Show Single Category. This is the winner, hands down. If your data is structured so that users can see all the documents in a category, then you can display just the contents of that category very quickly to the user. In some cases, it may make sense to let the user switch categories, in which case you have to consider whether or not he can see the contents of the other categories. But in most cases, the view would be something like My Sales and would show all the sales documents for the current user. The caveat for this kind of view is that the user interface for the Notes client is not quite as nice as the native view display. For Web browsers, it is just as good, and we have never seen a reason not to use this kind of view for Web browser applications. In fact, the performance is so good that it’s faster to open one of these with reader access controlled documents than to open a native view without reader access controlled documents!
Read more…
Viewed 8935 times by 2213 viewers
Don’t overwrite free space
This feature has not changed over the past few years, Lotus Notes and Domino Version. If you uncheck the box, then when the deleted files, Lotus Notes will be the actual cover, and not just the data pointer bit data. Our goal is to make the data recoverable. You will only use this option if your hard drive for personal security issues. For almost all applications, this extra physical security is not necessary, just an extra step, the data will be deleted.
Read more…
Viewed 5889 times by 1654 viewers
Don’t maintain unread marks.
If check this option in database properties, unread marks will not be tracked in your application regardless of the settings you have for each view. I’m used to track the time client_clock enabled database and I can see that I was surprised. For large application (about 20 GB with 200,000 documents), my Notes client could open the database in about five seconds without unread marks, including network traffic. With unread marks turned on, I had to wait an additional six seconds or more. This additional time was spent in GET_UNREAD_NOTE_TABLE and RCV_UNREAD. With unread marks turned off, these calls aren’t made.
Read more…
Viewed 7349 times by 1818 viewers
