Hi all,
I recognize my problem will be a bit difficult to understand. I’ll try…
We have one Lotus domain which is part of the mail infrastructure of our corporation. We are starting to create a global directory from MIIS (Microsoft) which has every email address of our company unless our own addresses which are on our local names.nsf. All works fine, but the global directory (based on pubnames.ntf, and with name namesglobal2.nsf) is creating thousand of administration requests on our admin4.nsf each time it is updated. These requests are cancelled, because the administrator user of namesglobal2.nsf has not permission for updating names.nsf, but it keeps our administration server busy all day, because it has to afford all these requests.
I don’t understand why is happening this issue and I don’t know how to avoid it.
Have you any idea or experience?
thanks
Subject: Administration requests not wanted
Check your admin help for Directory Assistance and
Integrating an Extended Directory Catalog into a primary Domino Directory
You can build an Extended Directory Catalog into an existing primary Domino Directory so that servers and users within the domain can use one, integrated corporate directory. Rather than create a new database from the PUBNAMES.NTF template in which to add the directory catalog configuration document and aggregate documents, instead create the configuration document in the primary Domino Directory (NAMES.NSF). All the original documents in the NAMES.NSF are retained, and the Dircat task adds documents aggregated from other Domino Directories into the database.
When you integrate an Extended Directory Catalog into a primary Domino Directory, a server within the domain of the primary Domino Directory searches the aggregated information automatically as part of its primary Domino Directory search, and so the use of directory assistance isn’t required. Person documents that the Dircat task aggregates are trusted for client authentication, and Groups documents that are aggregated can be used automatically for database authorization.
Servers outside the domain of the Domino Directory into which the Extended Directory Catalog is aggregated can use directory assistance to access the integrated directory. From the perspective of these servers, the integrated directory is a secondary directory that is searched after their primary Domino Directory; these servers only trust the integrated directory for client authentication, and can only use groups in the integrated directory for database authorization, if you set up the Directory Assistance document for the directory to allow this.
Dircat task processing affects only the documents the Dircat task aggregates from other Domino Directories, and not native documents that originate in NAMES.NSF. For example, rebuilding an Extended Directory Catalog that is integrated into a primary Domino Directory does not have any effect on the native documents.
You can remove an Extended Directory Catalog that is integrated into a primary Domino Directory by deleting the directory catalog configuration document, and then rebuilding the Extended Directory Catalog by running the dircat on it with the -r switch. Any native documents created outside of the aggregation process remain.
Hope this help
Subject: RE: Administration requests not wanted
Thanks a lot for your extensive answer, I will take it in account, and look carefully the documentation, thanks a lot.
In any case, do you know why is the adminp process trying to solve requests that are not for the names.nsf database? I don’t understand where it finds that a new database is being updated (In fact it is not included on the directory assistance yet)
Thanks again