Lotus Nut

Nope, I'm not talking about a blog for people into fast and furious 4 bangers (no offense to 4 banger drivers - like myself - who aren't fast or furious).

I'm talking about the new blog that IBMer Scott O'Keefe has started related to the Domino Configuration Tuner (DCT). You should go check it out at 'Tuner Blog. The first post is related to the "Check for Updates" option that's available with the template in which you can get the latest template from IBM as well as the latest updates to the rules. He also lists some of the new rules with the latest release.

You should really look into DCT if you haven't already. And with the 'Tuner Blog now active, I'm certain that Scott, et. al. will be looking for feedback!

Paul Mooney reminded us the other week that we should do this - and I agree! Over at Vaughan Rivett's blog, he's discussing some of the misunderstandings surrounding DAOS. He brings up several good points, but does question whether DAOS should be enabled on mail.box files. Of course, each situation may be a little different for every environment, so it's up to you to determine if you want to do this. But keep in mind that, like Vaughan states, DAOS is for any application - not just mail!

If I'm a daosified mail user and am using a CRM application to save a copy of an email message directly into the CRM, then if DAOS is enabled for the CRM application the attachment will be shared in DAOS! But if I want to send that email to a colleague and mail.box doesn't have DAOS enabled, then that attachment will be written to mail.box and then when it's delivered to the recipient's mail file DAOS would associate it as a duplicate from my mail file. But, if mail.box has DAOS enabled, then the attachment will never be pulled back out of DAOS (meaning there will not be the disk i/o associated with the transaction) and the router will know that it already existed in DAOS and not try to pull it back out. So, in most cases you will want to enable DAOS on your mail.box files. (Of course multiple server hops will not be aware of this currently, but for mail users on the same server it should be ok.)

Also remember that you'll need to enable transaction logging on your mail.box files. This may mean that you will need to disable the notes.ini settings for MailBoxDisableTXNLogging=1 and/or RM_NO_LOG_LARGE_OBJECTS=1. You will also need to manually enable transaction logging on the database with the router off by using load compact -T on each of your mail.box files.

Let's consider that for some reason your Connections server went down due to, say, a major power outage. Everything comes up ok except for Blogs (it could be another service as well, though) and you are getting the following error message:



When I was thinking about why this could be happening, I thought that either (a) there was a key file that was open but got corrupted, or (b) hopefully I just need to clear the Blogs cache directory because of corruption there. To make a long story short, it appears to have been a problem with the cache (whew...)!

The cache for a WAS server application is here:

[WAS_ROOT}\profiles\{Profile}\temp\{Node}\{application}

In this case it was:

C:\IBM\WebSphere\AppServer\profiles\myprofile\temp\mynode\BlogsServer

Basically, I shut down the server process, moved all of the files in the BlogsServer folder over to another location on the disk, and then started the server to let it create the temp files again. Thankfully, everything came back up alright. Oddly, the Homepage was rendering the blogs widget just fine - it was just the direct URL that wasn't working.

Domino 7.0.3 Fix Pack 1 is now available for download.

List of fixes for 7.0.3 Fix Pack 1

Information about Lotus Domino 7.0.3 Fix Pack 1

Download Fix Pack 1 (FP1) for IBM Lotus Domino 7.0.3