Archive for the ‘notes.ini’ Category

Using a Desktop Policy to set location document fields

Like most of you, I glean my information from various sources: Blogs, IBM Notes/Domino FAQ Newsletter, Notes Discussion forums at IBM, IBM technote searches, custom Notes/Domino google searches, Stumbleupon, delicious.com, and various other newsletters such as the searchdomino.techtarget.com or LotusUserGroup, etc.

I just recently signed up for LinkedIn and joined a few Notes/Domino groups. I haven’t done much with it yet, but here’s my public profile http://www.linkedin.com/in/davidkillingsworth.

Today, I received a LinkedIn post with an answer which pointed to Technote 1196837 – Using a Desktop Policy to set notes.ini and Location parameters.

I really wish I had seen this technote a very long time ago.

Performance Improvement – What do these Notes.ini variables do?

I was taking a look at this article at IBM.

I noticed that they added these variables to R6.5.x server:
NSF_DBCache_MaxEntries=4100
Server_pool_tasks=60
Server_max_concurrent_trans=60
Server_show_performance=1
Server_TransInfo_Range=9

and these notes.ini variables to 7.0x server:
NSF_DBCache_MaxEntries=4100
server_pool_tasks=60
server_max_concurrent_trans=60
server_show_performance=1
Server_TransInfo_Range=9
Cluster_replicators=3
FTUpdate_Idle_Time=25
Update_Idle_Time=25
EnableForcedFillOnFileExtend=1
NSF_DBCache_Max_Clean_Hold_Time=9999

Just wondering exactly what they do. It would have been nice if they would have explained the benefits of the performance improvement instead of just comparing the two versions of Domino.

Disabling “optional network drivers” Lan0, Com1, Com3

For a very long time, the “Optional Network Drivers” that Lotus forces you to install has been a very big thorn in my side.

Who uses anything besides TCPIP anymore?

I always disable any non TCPIP ports after install as it complicates Notes configuration for desktop support people, complicates location document creation, and I had one user once who had all the default ports enabled. He also had some network drives permanently mapped. When he was at a site that could not see the network mapped drives, and he would save an attachment, Notes would freeze.

After some study, I realized that Notes was trying to build the list of places to store the attachment for explorer and searching every possible port to map those drives.

I disabled everything except TCPIP for the guy and tried the same process. The guy thought I was Santa Claus and that he’d just received the best Christmas gift ever. The attachment save dialog window instantly opened and presented a local directory.

I’ve tried several ways to get around this on install (and there is no way to disable the ports by policies).
Read the rest of this entry »

LZ1 compression on 6.5.6 – Does it replicate?

I’m doing some testing on my Domino 6.5.6 FP3 servers.

I’ve got a bunch of mailboxes that did not already have LZ1 compression enabled (mostly archive mailboxes and a few mailboxes scattered around on remote servers). Mostly, it’s been turned on, and it’s definitely turned on in all of our mail.boxes.

The only reason that it is not turned on for all mailboxes up to this point is that we had to disabled it in our OpenNTF1.7b template because we have a couple of Mac OSX users. When design would run on the server at 1AM every night, the LZ1 property would be turned on for these 2 Mac users even though, we had manually turned it off. It was weird since, technote 1176010 entitled “Which Database properties are affected by a Design Replace or Refresh” clearly indicates that LZ1 compression is only affected by design replace and not design refresh.

These Mac OSX users would have problems with their attachments. There used to be technote number 1193756 on the issue, but it’s gone now. IBM must have fixed the issue and removed the technote.

I’ve enabled LZ1 compression for all databases now with the admin client (advanced properties).

Now, I’ve set the DEBUG_ENABLE_LZ1_REPAIR=1 in our * Configuration document so that it gets written to the notes.ini of all of our servers. Read the rest of this entry »

Pesky debugging and logging notes.ini settings

I’ve been investigating why our primary mail routing hub server is taking so long to route messages recently. The behavior started a few days ago (or maybe it’s been going on for a while and we didn’t notice it).

  • Messages will queue in the mail.boxes for anywhere from 5 to 15 (maybe longer) minutes.
  • They do NOT have the -check in progress- (which sometimes take place when Trend Micro ScanMail or IQSuite, our mail compliancy capturing software, is holding up the router).
  • Then suddenly they all route at once.
  • Then the process will start over again.

Read the rest of this entry »

Consulting

I'm currently available
for Lotus Notes / Domino consulting engagements.

LinkedIn

Connect with me:

LinkedIn

Advertisement
Advertisement
Categories