Posts Tagged ‘Designer’
Where to set where an agent runs.
A few months ago, I setup a “Directory” server. This server is meant to be the administration server for names.nsf, it also serves as an LDAP service for our corporate phone directory, it also runs the directory cataloger service, and it is our registration server (where all the admins register new users and update groups). This keeps things nice and tidy and all updates happening in one location.
If you use Directory Catalog (dc.nsf), there is an agent that you can turn on that runs once a week at 2:00AM on Sundays that gives some statistics on names.nsf versus dc.nsf, the fields that are used in dc.nsf, the size, etc. etc and then sends that report to the administrators group or group of your choosing. To receive the report you simply supply a group name in the ” Send Directory Catalog reports to:” field in the Directory Catalog configuration document (configuration view of dc.nsf).
For months, I couldn’t figure out why this agent was running on the old server which used to run the dircat task instead of the new directory server.
By accident, I discovered where that configuration was hiding. I should have known this, but sometimes it’s not always obvious.
Upgrading the design of the NAB, replication and designer gotchas.
I’m writing this post to help some soul out there. There are lots of organizations that get themselves into multiple Domino point release upgrades and avoid upgrading the design of their NAB because it’s too much work, or they’ve forgotten the design changes they’ve made and don’t want to break anything, or too busy, or….
Our organization was in that state, and I’ve been working for the last 2 weeks to find the changes, customize a clean 6.5.6 template and roll it out. It’s actually been a pretty large chunk of work getting it right.
I found a big gotcha today when I tried to roll it out to my production environment.
Read the rest of this entry »