Замечание к документу "Настроить все заново"   >>>   
Тема: 1.Процесс объединения доменов описан в KB; 2. в 5.01 был затык с новыми возможностями заверителя

Создан:Andrey V. Dmitriev 07/11/2000 07:10 AM
Модифицирован:Andrey V. Dmitriev 07/11/2000 07:15 AM
Папка:
09. Администрирование Notes & Domino		Тип сообщения:
Решение
Сообщение:
посему >>>необходимо<<< проапгрейдить серверы до хотябы до 5.03 и почитать справку администратора по настройке ID Recovery
и почитать из KB документы с номерами 156000 и 155985

На всякий случай цитирую:

156000
Merging Domino Domains Into One
by Barbara Burch and Rob Slapikoff

Overview

Any successful company usually goes through some growing pains, from changes in staffing and resources, to perhaps acquiring another organization. As your company grows, you need to make sure that your Domino and Notes deployment grows with it. If you've acquired a company with its own Domino domain, or if you have multiple domains within your own company, it's a good idea to assess whether you should merge those separate Domino domains into one. The good news is that there's nothing painful about merging your domains, as this article will show you. Y ou must simply follow a methodical process for absorbing one domain's address book into another.

A Domino domain is essentially defined by the Public Address Book. Among other things, the Public Address Book provides a central directory of Domino servers, users, certifiers, domains, groups, connections, and profiles. All servers in a domain share the same Public Address Book. An administrator with appropriate access to the Public Address Book can easily manage administrative functions for an entire domain, even if it extends over a large geographic area. A new domain is created whenever you choose "first server setup" during the Domino server Setup program.

The benefits to having a single domain -- and therefore, a single Public Address Book -- include:

* Mail addressing is easier.
* Mail routing is easier. (Mail routes automatically within a domain between servers in the same Notes named network. You only have to create Connection documents for mail routing when servers do not have a protocol in common.)
* You can use the Administration Process for automating tasks. (The Administration Process works only within a single domain.)

However, you do not have to merge the domains. Keeping multiple domains in your organization means that you can keep the size of the Public Address Book down and give more control to each domain over its own address book. You can then set up directory assistance by creating a Master Address Book or set up cascading Public Address Books. For more information on managing multiple Public Address books, please see the Administration Help (HELPADMN.NSF).

This article will walk you, the Domino administrator, through the steps for merging multiple domains into one. Again, this means simply merging the separate address books into one composite Public Address Book for the domain. You should remember that changing a domain name only affects mail. It has nothing to do with replication, certification, or naming. The end of this article discusses some ways you might want to customize the merge process, perhaps by using the Administration Process to change the certification of your users and servers.


Merging the XYZ domain into the Acme domain

Let's say that the Acme Company has recently acquired XYZ Inc. and would like for all servers and users to reside in the Acme domain. The original XYZ domain will become obsolete. Most of the actual merging work you'll do offline, so both domain's servers and clients can keep operating as usual.

Step 1: Modifying the Acme Public Address Book

Complete the following steps on any client in the Acme domain.

1. Create a local replica of the Acme Public Address Book. Choose File - Replication - New Replica. Select "Local" for the Server name, change the filename to "ACMENAME.NSF," and click OK. (If you don't rename the address book to something other than NAMES.NSF, you will overwrite the Personal Address Book on that machine.)

2. Disable replication for your local replica of the Acme address book, so your intermediate changes aren't replicated back to a server. To do this, select the database, choose File - Replication - Settings, click Other and select "Temporarily disable replication."

3. Open the XYZ Public Address Book.

4. Copy and paste all of the documents from the XYZ address book into your local copy of the Acme address book. One way to make this easier is to create a view that shows all the documents. To do this, choose Create - View, name the view "All Docs," select "Select by formula" and type "SELECT @All."

5. Using your new "All Docs" view in the XYZ address book, select all the documents and copy them. (Choose Edit - Copy.) Then, paste them into your local replica of the Acme Public Address Book.

6. In your local copy of the Acme address book, create an agent to modify documents from the XYZ domain to reflect the new domain name, "Acme." Choose Create - Agent, name the agent "Fix Domain," select for the agent to act on "All documents in database," and enter the following formula.

FIELD Domain:=@If((Type="Server":"Location");@If((Domain="XYZ");
"Acme";Domain);@Unavailable);
FIELD MailDomain:=@If((Type="Person":"Database":"Resource");
@If((MailDomain="XYZ");"Acme";MailDomain);@Unavailable);
FIELD SourceDomain:=@If((Type="Connection");@If((SourceDomain=
"XYZ");"Acme";SourceDomain);@Unavailable);
SELECT @All

7. Run your agent on all the documents in your local copy of the Acme address book. After you run the agent, all domain references in documents that you may need to keep should be changed from XYZ to Acme.

8. Open the Server - Domains view and review the Domain documents. Delete any that are unnecessary. (Domain documents are for allowing or restricting routing through domains, so you will no longer need any between Acme and XYZ. Also, domain documents define other domains, such as gateway domains. So, some of these documents might now be redundant, and unnecessary.)

9. Open the Groups view. Check for redundant group names, and merge or delete as necessary.

10. Open the Server - Configurations view. Check for redundant configuration names, and merge or delete as necessary.

11. Open the Server - Mail-in Databases and Resources view. Check for redundant mail-in database or room/resource names, and correct any names as necessary.

NOTE: You'll evaluate the Connection documents later, when all servers are running with the merged Acme address book.


Step 2: Replicating the new Acme Public Address Book to servers in the Acme domain

After you complete the changes in the Acme Public Address Book, you're ready to put the address book to use in the current Acme domain. Complete the following.

NOTE: You should complete these steps over a weekend, a time when the domain activity will be at its lowest. The views for the Public Address Book will have to be updated on each server, which could affect performance.

1. Replicate the Acme Public Address Book to all servers in the Acme domain. The servers will then be running with the new combined address book, and you can verify that the new address book does not cause any problems. The XYZ domain remains up and running as its own domain.

2. If you don't have any problems with the new address book, you're ready to distribute it to the old XYZ domain. If your company extends over a large geographic area and you want to save network costs, you can copy the NAMES.NSF and ADMIN4.NSF files either onto a file server or CD for transferring to servers in the XYZ domain. (To use the Administration Process in the new, merged domain, you must have only one replica of the Administration Requests database (ADMIN4.NSF) in the domain.)


Step 3: Getting the new Acme Public Address Book to servers in the old XYZ domain

Complete the following for servers and users that reside in the XYZ domain.

NOTE: You should complete these steps over a weekend, a time when the server activity will be at its lowest. Also, because you will be bringing down each server in the domain, it's a good time to upgrade to the latest release.

1. On any server, create a backup copy of the existing XYZ Public Address Book and Administration Requests database (ADMIN4.NSF). It's a good idea to rename the files and place them in a separate directory.

2. Complete the following on each server in the XYZ domain.

* Shut down the Domino server.
* Obtain copies of the Acme Public Address Book (NAMES.NSF) and Administration Requests (ADMIN4.NSF) files. You can either replicate the files to the workstation, or if provided, obtain the files from a file server or CD.
* Replace the existing XYZ domain's NAMES.NSF and ADMIN4.NSF files with ones for the Acme domain (that is, copy the Acme Public Address Book (NAMES.NSF) and Administration Requests (ADMIN4.NSF) files over the existing ones).
* Restart the server, and it will now be running in the Acme domain.


Step 4: Updating Connection documents

Now, you can complete the changes in the Acme Public Address Book. Open the Server - Connections view and evaluate the Connection documents, to see if they are still necessary. (Connection documents are necessary for mail routing between different domains or different Notes named networks, so you may no longer need them in the new merged domain.) Complete the following.

* If a Connection document is only for mail routing, and has "XYZ" as the Destination domain, delete it if the servers in question are on the same Notes named network. If the servers are on different Notes named networks, change the Destination domain to "Acme."

* If a Connection document is for both mail routing and replication, modify the Tasks field to only be for Replication if the servers in question are on the same Notes named network. If the servers are on different Notes named networks, change the Destination domain to "Acme."

* If a Connection document is only for replication, and has "XYZ" as the Destination domain, change the Destination domain to "Acme."


Step 5: Creating a mail message to automatically update users' Personal Address books

After each server is running with the Acme Public Address Book, you can get users who formerly resided in the XYZ domain to update their Personal Address books with the new domain name, "Acme." An easy way to do this is by sending a Notes mail message to users with a button that they must simply click to update their Personal Address books. To do this, complete the following steps.

1. Create a new mail memo.

2. In the body of the memo, create a new button.

3. Select Script radio button for the formula type.

4. Paste the following code into the Declarations Event.

' System variables -> DO NOT CHANGE!!!!
Const VIEW_LOCATION_NAME = "($Locations)"
Const VIEW_CONNECTION_NAME = "($Connections)"

'Application variables -> EDIT THESE ONES!!!!
Const OLD_DOMAIN_NAME = "XYZ" ' This is the value of your old domain
Const NEW_DOMAIN_NAME = "Acme" ' This is the value of your new domain

5. Paste the following code into the Click Event.

Dim session As New NotesSession
Dim dbNab As NotesDatabase
Dim view As NotesView
Dim note As NotesDocument
Dim sNamesLine As String
Dim nPos As Integer
Dim sDomainValue As String
Dim bNeedsUpdate As Integer
Dim bLocationModified As Integer

On Error Resume Next

' first, get the local NAB
sNamesLine = session.GetEnvironmentValue("names",True)

nPos = Instr(sNamesLine, ",")
If nPos > 0 Then
sNamesLine = Left$(sNamesLine, nPos-1)
Else
sNamesLine = "names.nsf"
End If

Set dbNab = New NotesDatabase( "",sNamesLine )

If Not(dbNab.isOpen) Then
Messagebox("Could not locate your Name & Address book.")
Exit Sub
End If

' update all location documents
Set view = dbNab.GetView(VIEW_LOCATION_NAME)
If (view Is Nothing) Then
Messagebox("Your Name & Address book is missing a required view.")
Exit Sub
End If

Set note = view.GetFirstDocument

While Not(note Is Nothing)
sDomainValue = note.Domain(0)
If Lcase(sDomainValue) = Lcase(OLD_DOMAIN_NAME) Then
note.Domain = NEW_DOMAIN_NAME
Call note.save(True,False)
bLocationModified = True
End If
Set note = view.GetNextDocument(note)
Wend

If (bLocationModified) Then Messagebox("You need to restart Notes in order for these changes to take place.")

' update all connection documents
Set view = dbNab.GetView(VIEW_CONNECTION_NAME)
If (view Is Nothing) Then
Messagebox("Your Name & Address book is missing a required view.")
Exit Sub
End If

Set note = view.GetFirstDocument

While Not(note Is Nothing)
bNeedsUpdate = False
sDomainValue = note.SourceDomain(0)
If Lcase(sDomainValue) = Lcase(OLD_DOMAIN_NAME) Then
note.SourceDomain = NEW_DOMAIN_NAME
bNeedsUpdate = True

End If
sDomainValue = note.DestinationDomain(0)
If Lcase(sDomainValue) = Lcase(OLD_DOMAIN_NAME) Then
note.SourceDomain = NEW_DOMAIN_NAME
bNeedsUpdate = True
End If
If (bNeedsUpdate) Then Call note.save(True, False)
Set note = view.GetNextDocument(note)
Wend

6. Complete the memo by instructing users to simply click the button, which will update the domain references in their Personal Address books.

7. Send the memo to the appropriate users. When the recipients click the button, the domain values will be updated, if necessary.


Customizing this example

You can customize this example in many ways; it all depends on your situation. For example, if you plan to change the hierarchical naming and/or certification for the domain, you can use the Administration Process to automate the tasks. (You must still manually change server names and update other documents.) To do this, you must have the Administration Process correctly set up and running on all servers in the domain, with administration servers assigned and so on. For the specific steps for using the Administration Process, please see the Administration Help (HELPADMN.NSF).

Some other administration databases, such as the Statistics and Events (EVENTS4.NSF) database, have domain references that will need to be eventually modified. All of these databases will work correctly without updating the domain name. However, you should update the domain name sometime in the future.

Remember that you should notify all outside companies that route mail to you about any domain name changes, so they can change the domain reference in their Connection documents. Also, be aware of any application design that may include the old domain name.


================================================================================

About the Author
Rob Slapikoff is the senior developer of the Notes system templates at Iris. He has been involved with Notes since version 1.0 when, while working in Lotus Customer Support, he developed the first support tracking application in Notes. Rob joined Iris in the Summer of 1993 as an internal support engineer and now runs our internal Notes network. He is responsible for the Address Book, catalog, certlog, log admin4 and other systems template designs.

155985

Title: Procedure for Merging Notes 4.x Domains (Documents to Consider and Procedural Checklist)

Product Area: Notes
Product: Notes 4.x
Topic: Server \\ Performance
Number: 155985
Date: 03/12/98



DOCUMENTS TO CONSIDER WHEN PLANNING A MERGE


You must thoroughly plan the process of merging domains before you actually make any changes. The administrator needs to consider every place that a domain is referenced.

PUBLIC ADDRESS BOOK

When merging domains, you are creating one Public Address Book for the entire domain. Every reference to a merged domain has to be modified. Every irrelevant document and reference needs to be removed. When the process is complete, there should be no reference to the old domain. The following documents contain references to domains:

Server documents
Connection documents
Domain documents
Person documents
Location documents
Mail-in database documents
Group documents (LocalDomainServers, OtherDomainServers)

PERSONAL ADDRESS BOOK

The following documents contain references to domains:

Location documents
Group documents (LocalDomainServers, OtherDomainServers)

OTHER REFERENCES

CERTLOG.NSF
ADMIN4.NSF
EVENT4.NSF
STATREP.NSF
Domains=domainname in NOTES.INI


PROCEDURAL CHECKLIST

You will need to take at least the following steps to merge two domains:

1. Determine which domain remains the same, and which one gets renamed.

2. Identify all the documents in the Public Address Book of the merging domain that will need to be modified.

3. Bring down the servers and clients.

4. Backup the Public Address Books in both domains.

5. Bring up the servers and clients.

6. Turn off scheduled replication.

7. Modify all documents in the Public Address Book of the merging domain to reflect the new domain name.

8. Delete Connection documents that are no longer relevant in the merging domain.

9. Delete Adjacent Domain and Non-adjacent Domain documents that are no longer relevant.

10. Copy and paste modified documents from the Public Address Book of the merging domain to the Public Address Book of the unchanged domain.

11. Change the "DOMAIN=" line in the NOTES.INI file.

12. Test the new Public Address Book.

13. Make a replica of the Public Address Book on all servers in the domain.




Synonyms: pab, address book, name & address book, nab, NAB

(C) Copyright 2000 Lotus Development Corporation. All rights reserved.


Иерархия документов данной дискуссии:
Хочу перевести организацию на новый домен (Aleksey S. Kalushevskiy) (10.07.2000 10:20:34)
.... Если имется ввиду переименование Domino сервера, то все просто, за Вас это все сделает процесс администрирования... (Vitaliy V Nekrasov; NSrv2500) (10.07.2000 20:01:14)
........ Настроить все заново (Aleksey S. Kalushevskiy) (10.07.2000 20:18:34)
............ 1.Процесс объединения доменов описан в KB; 2. в 5.01 был затык с новыми возможностями заверителя (Andrey V. Dmitriev) (11.07.2000 7:10:05)
............ Ну тут ничего страшного нет :) (Vitaliy V Nekrasov; NSrv2500) (11.07.2000 14:15:49)
................ А если я пересертифицирую пользователя с использованием сертификата сервера 5.0.3. смогу ли я восстанавливать забытые пароли? (Aleksey S. Kalushevskiy) (12.07.2000 15:00:19)
.................... В любой файл (R5) Вы всегда можете добавить информацию об восстановлении ID, см. док. по восстановлению ID файлов. Ресертификация только заменит в ID сертификат и отношения в восстановлению не имеет, это отдельный процесс. (Vitaliy V Nekrasov; NSrv2500) (14.07.2000 17:56:12)
................ Административный процесс не переподписывает элементы дизайна (Aleksey S. Kalushevskiy) (04.08.2000 17:06:24)


Разработчикам и администраторам: курсы, книги, сертификация