Novell GroupWise. www.novell.com 6.5 | MULTI-SYSTEM ADMINISTRATION GUIDE September 30, 2004 Novell. Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside. Copyright © 2003-2004 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. U.S. Patent Nos. 5,412,772; 5,701,459; 5,717,912; 5,760,772; 5,870,739; 5,873,079; 5,884,304; 5,903,755; 5,913,209; 5,924,096; 5,946,467; 5,963,938; 6,081,804; 6,138,170; 6,167,393; 6,192,405; 6,216,123; 6,546,433; 6,584,458; D393,457; and Patents Pending. Novell, Inc. 1800 South Novell Place Provo, UT 84606 U.S.A. www.novell.com GroupWise 6.5 Multi-System Administration Guide Sepbember 30, 2004 Online Documentation: To access the online documentation for this and other Novell products, and to get updates, see www.novell.com/documentation. Novell Trademarks ConsoleOne is a registered trademark of Novell, Inc. in the United States and other countries. eDirectory is a trademark of Novell, Inc. Group Wise is a registered trademark of Novell, Inc. in the United States and other countries. NetWare is a registered trademark of Novell, Inc. in the United States and other countries. NLM is a trademark of Novell, Inc. Novell is a registered trademark of Novell, Inc. in the United States and other countries. Third-Party Trademarks All third-party trademarks are the property of their respective owners. Contents About This Guide 7 Parti Connecting to GroupWise 5.x and 6.x Systems 1 Understanding Connection Options 11 Connection Methods Supported by the Various GroupWise Versions . . ........................ 11 Dynamic Internet LINKS: à 5 gen eee ee a ee ee A ee oe ee et ee 2 NS 12 Direct: LINKS: 4.44 oe be ee Pee A A Sey se eae BS el ee A ee Ba a we eee 12 Gateway’ GINKS 85 tena e eae e ne Abo nek Bae ee EOS See Due ee Robe alg eG: np lua es pee we 12 2 Using Dynamic Internet Links 13 MTA Version Requirements: 212.5 eon + eed Sb Re A tee BREE eRe De eee oh RS 13 Installing the GroupWise Internet Agent ......................................... 13 Setting Up Internet-Style Addressing. . ......................................... 14 Adding MTA Resource Records to DNS ......................................... 14 Creating the Address ("A") Record .......................................... 14 Creating the Service ("SRV") or Text ("TXT") Record ................................ 15 Configuring the MTA’s Server for DNS Lookups . .................................... 16 Configuring a NetWare 6.x, 5.x, or 4.x Server for DNS Lookups . .......................... 16 Configuring a Windows NT Server for DNS Lookups. . ............................... 16 Configuring a Windows 2000 Server for DNS Lookups. ............................... 16 Enabling MTAs to Perform DNS Lookups ........................................ 17 Enabling DNS Lookups for AI MTAS ......................................... 17 Enabling/Disabling DNS Lookups for Individual MTAS ................................ 18 Understanding Dynamic Internet Links. . ........................................ 19 Stage 1: GroupWise Client in the Sending System. ................................. 19 Stage 2: GroupWise Client in the Sending System. ................................. 19 Stage 3: GroupWise MTA in the Sending System .................................. 20 Stage 4: GroupWise MTA in the Sending System .................................. 20 Stage 5: GroupWise MTA in the Sending System .................................. 20 Stage 6: GroupWise MTA in the Sending System .................................. 20 Stage 7: GroupWise Internet Agent in the Sending System ............................. 20 Stage 8: GroupWise Internet Agent in the Sending System ............................. 20 Stage 9: GroupWise MTA in the Sending System .................................. 21 Stage 10: GroupWise MTA in the Sending System. . ................................ 21 Stage 11: GroupWise MTA in the Receiving System. . ............................... 21 Stage 12: Both GroupWise MTAS. .......................................... 21 3 Using Direct Links 23 OVEIVIEW. mk eA ee ae LA PES Be Lee bee ae Ph eee Le Klan 23 Creating'an:ExXtérnal Domaine. szor west Be ee EG ee Ap Be OR SE 24 Linking to the External Domain. ... 2... 1... 2 ee 25 Checking the Link Status of the External Domain .................................... 26 Sending Messages Between Systems . ......................................... 27 Exchanging Information Between Systems. ....................................... 27 Message Flow Between External Domains. ....................................... 27 Contents 5 4 Using Gateway Links Connecting Systems Through the Internet ........................................ Connecting Systems Through an Asynchronous Phone Line. . ............................. Connecting Systems Through an X.25 Line. ....................................... Connecting GroupWise Systems Through Other E-Mail Systems . ........................... Part Il Connecting to Non-GroupWise Messaging Systems 5 GroupWise Internet Agent 6 GroupWise Gateways Part II Merging with GroupWise 5.x and 6.x Systems 7 + Why Merge GroupWise Systems? 8 Planning the Merge Understanding the Merge Process . o arane ck vom a pue Planning Administrator Rights .............................................. Determining Which GroupWise Objects Are No Longer In Use. ............................. Planning the Location of the Domain Database Backup Directories . .. .... .................... Planning GroupWise System Connections ........................................ External Domains... + 1 5 8 e406 à à eae ode ee E a ee ee ee pp ee eB ee econ vee Linking thé Domains... 2 244) Sls. ey lp Seok tb ee a e aS Eat ee MG Ale eine eS ae Releasing the Secondary Domains in Site #2..................................... Planning to Merge Additional GroupWise Systems . ................................... Merging in One Session: : s 2, 54. 4 ee ee da à da mehelt ee ee ee be Merging at Different Times. . ............................................. Merge Planning Worksheet . ............................................... 9 Preparing for the Merge setting: Up Administrator RIghts 2-22 45 mt ead Aan Soe Sek ee s A nn nes PE Deleting Unused GroupWise Objects . .......................................... Verifying That UNC Paths Are Correct . ......................................... Resolving Pending Operations . . ............................................ 10 Merging the GroupWise Systems Creating External Domains for Both Systems. . ..................................... Creating Site #1 External Domains in Site #2..................................... Creating Site #2 External Domains in Site #1. .................................... Configuring Links Between Site #2 Domains and Site #1 Secondary Domains. . .................... Checking Links to External Domains for Both Systems. . ................................ Checking Links to Site #1 External Domains in Site #2 ................................ Checking Links to Site #2 External Domains in Site #1 . ................................ Creating Temporary Holding Directories . ........................................ Releasing Site #2 Secondary Domains . ......................................... Sending Site #2 Databases to the Site #1 Administrator... .............................. Receiving Site #2 Databases at Site #1. ......................................... Merging a Site #2 Domain into Site #1 . ......................................... Merging the Next GroupWise System. .......................................... Sending the Merged Site #2 Databases to Site #2 .................................... Restarting the GroupWise Agents. ............................................ Testing the Merged'System: : «res doe OE ee ee eee ae Part IV Documentation Updates september 302004; mess eS Bon ey eae ee es eee eee EB RE AO ie eee ete BS 6 GroupWise 6.5 Multi-System Administration Guide 29 29 30 30 30 33 35 About This Guide This Novell? Group Wise” 6.5 Multi-System Administration Guide helps you connect your Group Wise system to other Group Wise systems or non-Group Wise messaging systems, and helps you merge your Group Wise system with another GroupWise system to create one system. The guide is divided into the following sections: “Connecting to GroupWise 5.x and 6.x Systems” on page 9 “Connecting to Non-Group Wise Messaging Systems” on page 31 “Merging with GroupWise 5.x and 6.x Systems” on page 37 Additional Documentation For additional Group Wise documentation, see the following guides at the Novell Group Wise 6.5 documentation Web site (http://www.novell.com/documentation/gw65): * Installation Guide + Administration Guide + Interoperability Guide + Troubleshooting Guides + GroupWise Client User Guides Documentation Updates For the most recent version of the GroupWise 6.5 Multi-System Administration Guide, visit the Novell GroupWise 6.5 documentation Web site (http://www.novell.com/documentation/gw65). Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. A trademark symbol e, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. User Comments We want to hear your comments and suggestions about this manual and the other documentation included with GroupWise. To contact us, please use the User Comment feature at the bottom of each page of the GroupWise online documentation. About This Guide 7 GroupWise 6.5 Multi-System Administration Guide Connecting to GroupWise 5.x and 6.x Systems Chapter 1, “Understanding Connection Options,” on page 11 Chapter 2, “Using Dynamic Internet Links,” on page 13 Chapter 3, “Using Direct Links,” on page 23 Chapter 4, “Using Gateway Links,” on page 29 Connecting to GroupWise 5.x and 6.x Systems 9 10 GroupWise 6.5 Multi-System Administration Guide Understanding Connection Options When connecting your Group Wise” 6.x system with another Group Wise 5.x or 6.x system, you can choose from several connection methods. To help you choose the best method for your system, the following sections provide brief summaries: + “Dynamic Internet Links” on page 12 + “Direct Links” on page 12 + “Gateway Links” on page 12 Depending on the versions of the two Group Wise systems you are trying to connect, some of the methods might not be available. For information about methods available for the two systems you are connecting, see “Connection Methods Supported by the Various GroupWise Versions” on page 11. Connection Methods Supported by the Various GroupWise Versions The following chart lists the GroupWise 5.x and 6.x versions and the methods that can be used when connecting systems that are these versions. 5.0 5.1 5.2 5.5 5.5 EP 6.x 5.0 DG DG DG DG DG DG 5.1 DG DG DG DG DG DG 5.2 DG DG DG DG DG DG 5.5 DG DG DG IDG IDG IDG 5.5 EP DG DG DG IDG IDG IDG 6.x DG DG DG IDG IDG IDG KEY D = Direct Link G = Gateway Link I = Dynamic Internet Link To use the chart, locate your system’s version in the first column, then read across the row until you reach the version of the system you are connecting to. The methods listed are the methods supported when connecting the two systems. IMPORTANT: A GroupWise system's version is determined by the version of the Message Transfer Agent (MTA) running in the system. If your system includes multiple versions of the MTA, determine which MTA will be used when connecting to the other system and use that MTA's version when reading the table. Understanding Connection Options 11 Dynamic Internet Links Direct Links The dynamic Internet link capability of the Group Wise Message Transfer Agent (MTA) enables it to use Domain Name Service (DNS) to associate the domain name in an Internet-style address (for example, jsmith@novell.com) to an MTA assigned to receive messages for that domain name. After the address has been resolved, the sending MTA uses the Group Wise Message Transfer Protocol (GWMTP) to connect with and transfer messages to the destination MTA. Because messages are transferred directly from one MTA to another, no GroupWise client functionality is lost. Users can perform Busy Searches, retract sent messages, and see the status of their outgoing messages, just as if the recipient were in the same Group Wise system. In addition, users are able to use well-known Internet-style address syntax (for example, jsmith@novell.com). Administratively, using dynamic Internet links enables you to avoid defining users from other Group Wise systems in your Group Wise system. As long as the sender knows the recipient’s Internet-style address, and the recipient’s domain name is registered in DNS and associated with an MTA, the message will be properly routed to the recipient. For information about connecting Group Wise systems via dynamic Internet links, see Chapter 2, “Using Dynamic Internet Links,” on page 13. The direct link capability of the MTA enables it to use a mapped or UNC path to access a domain directory in another GroupWise system or to use TCP/IP to connect to the domain’s MTA. This is the same functionality that enables two domains in the same GroupWise system to be connected. Because messages are transferred directly from one MTA to another, no GroupWise client functionality is lost. Administratively, you can use the External System Synchronization feature to exchange information between the two systems and enable users to select addresses from the Address Book, or you can choose to not exchange information and require users to enter a fully-qualified address (userID.post_office.domain or user@host). For information about connecting GroupWise systems via direct links, see Chapter 3, “Using Direct Links,” on page 23. Gateway Links 12 If you can’t establish a direct link (mapped path, UNC path, or TCP/IP connection) between domains in two systems, you can use a GroupWise gateway to link the two systems. Depending on the gateway used, some GroupWise functionality might not be available when sending messages between systems. For information about connecting GroupWise systems via gateways, see Chapter 4, “Using Gateway Links,” on page 29. GroupWise 6.5 Multi-System Administration Guide Using Dynamic Internet Links You can connect two GroupWise® systems through dynamic Internet links. Dynamic Internet links enable a GroupWise Message Transfer Agent (MTA) to use Domain Name Service (DNS) and GroupWise Message Transfer Protocol (GWMTP) to send messages from one system to anther. For an overview of dynamic Internet links, see Chapter 1, “Understanding Connection Options,” on page 11. To use dynamic Internet links, complete the tasks in the following sections: + “MTA Version Requirements” on page 13 + “Installing the GroupWise Internet Agent” on page 13 + “Setting Up Internet-Style Addressing” on page 14 + “Adding MTA Resource Records to DNS” on page 14 + “Configuring the MTA’s Server for DNS Lookups” on page 16 + “Enabling MTAs to Perform DNS Lookups” on page 17 For a general explanation of how dynamic Internet links work, see “Understanding Dynamic Internet Links” on page 19. MTA Version Requirements To use dynamic Internet links to connect your GroupWise system with another GroupWise system, both GroupWise systems must have at least one domain that is running one of the following versions of the GroupWise MTA: * GroupWise 5.5 + GroupWise 5.5 Enhancement Pack + GroupWise 6.x Versions of the MTA prior to version 5.5 do not support dynamic Internet links. Installing the GroupWise Internet Agent Before configuring your GroupWise system to use dynamic Internet links, you need to make sure that the Group Wise Internet Agent has been installed. Dynamic Internet links require that your GroupWise system be using Internet-style addressing, which is only available if you’ve installed the Internet Agent and created one or more Internet domains for your GroupWise system. The only requirement is that the Internet Agent be installed so that an Internet Agent object is created in Novell® eDirectory™. The Internet Agent does not actually need to be configured correctly or running. However, if there are GroupWise systems that you need to connect to but Using Dynamic Internet Links 13 cannot do so through dynamic Internet links, you can use the Internet Agent to connect to those systems while using dynamic Internet links to connect to supported Group Wise systems. For information about installing the Internet Agent, see “Installing the Group Wise Internet Agent” in the GroupWise 6.5 Installation Guide. Setting Up Internet-Style Addressing Dynamic Internet links require your GroupWise system to be configured to use Internet-style addressing (user@hostname) rather than standard Group Wise addressing (userID.post_office.domain). If you have not enabled Internet-style addressing and defined at least one Internet domain for your GroupWise system, see “Internet-Style Addressing” in the GroupWise 6.5 Administration Guide. The Internet domains you establish when setting up Internet-style addressing (for example, novell.com, groupwise.novell.com, and support.novell.com) are the key to enabling dynamic Internet links. Each MTA that will receive messages must be defined in DNS and associated with the Internet domain (or domains) that it will receive messages for. This allows MTAs in other Group Wise systems to route messages that contain your Internet domain names to the appropriate MTAs in your system. Adding MTA Resource Records to DNS In order for your GroupWise system to receive messages from another GroupWise system via a dynamic Internet link, you need to create a DNS resource record for at least one of your MTAs. The resource record enables the MTA’s address, along with the Internet domain names associated with it, to be broadcast throughout the Internet. You need to create the following resource records in DNS: + An address ("A") record that maps the MTA server’s host name to its IP address. + A service ("SRV") record or a text ("TXT") record that maps the Internet domain name to the host name or IP address assigned to the MTA’s server. You can use your tool of choice to modify DNS. The following sections explain the information required and provide sample records. + “Creating the Address ("A") Record” on page 14 + “Creating the Service ("SRV") or Text ("TXT") Record” on page 15 Creating the Address ("A") Record 14 You can create an "A" record to map your MTA server’s fully-qualified host name to its IP address. Doing so enables you to use the server’s fully-qualified host name in the service ("SRV") or text ("TXT") record rather than the IP address. The "A" record is required if you plan to use a "SRV" record. The following text shows sample "A" records. ; Address ("A") records i localhost IN A 123.03: Os corp.serv.novl IN A 123.456.78.90 GroupWise 6.5 Multi-System Administration Guide gwdev.serv.novl IN A 123.456.78.91 gwsup.serv.novl IN A 123.456.78.92 Host Name (column 1): Use the host name assigned to the MTA’s server. In the above example, corp, gwdev, and gwsupport are the host names assigned to three MTA servers. Class (column 2): Use IN to represent the Internet. Type (column 3): Use A to specify an address record. IP Address: Use the IP address assigned to the MTA’s server. Creating the Service ("SRV") or Text ("TXT") Record You can use either service records or text records to map your Internet domain names to MTAs. The following text shows sample "SRV" and "TXT" records: i ; Service ("SRV") records ; gwmtp.tcp.novell.com 172800 IN SRV "1 0 7100 corp.serv.novl" gwmtp.tcp.groupwise IN SRV "1 1 7100 corp.serv.novl" gwmtp.tcp.groupwise IN SRV "1 2 7100 gwdev.serv.novl" gwmtp.tcp.support 172800 IN SRV "1 0 7100 gwsup.serv.novl" gwmtp.tcp.support 172800 IN SRV "2 0 7100 corp.serv.novl" i ; Text ("TXT") records r gwmtp.tcp.novell.com 172800 IN TXT "1 0 7100 corp.serv.novl" gwmtp.tcp.groupwise IN TXT "1 1 7100 corp.serv.novl" gwmtp.tcp.groupwise IN TXT "1 2 7100 gwdev.serv.novl" gwmtp.tcp.support 172800 IN TXT "1 0 7100 gwsup.serv.novl" gwmtp.tcp.support 172800 IN TXT "2 0 7100 corp.serv.novl" Service. Protocol. Name (column 1): The service must be specified as gwmtp. The protocol must be specified as tcp. The name corresponds to the Internet domain name you want associated with the MTA. In the above sample, novell.com, groupwise.novell.com, and support.novell.com are the Internet domain names defined in GroupWise. Time to Live (column 2): TTL (time to live) is the amount of time the record is cached in memory so it doesn't have to be looked up again. TTL is specified in seconds. In the above sample, 172800 represents 2 days. If you don’t specify a TTL, the record is not cached. Class (column 3): Enter IN to represent the Internet. Type (column 4): Enter SRV to specify a service record. Enter TXT to specify a text record. Priority (column 5): If an Internet domain name is associated with two different MTAs, the host with the lowest value is always contacted first. For example, a host with priority 1 is contacted before a host with priority 2. If two records with the same Internet domain name have the same priority, the weight number is used. In the above example, the two groupwise.novell.com records have the same priority, so the weight would be used. Weight (column 6): The weight number specifies how to allocate connections among hosts with equal priorities. In the groupwise.novell.com record above, the corp. serv.nov1 host and the gwdev.serv.novl host have equal priorities, but the corp. serv.nov1 host has a weight of 1 and the gwdev.serv.nov1 host has a weight of 2. This means that 1 out of 3 times the Using Dynamic Internet Links 15 corp.serv.novl host would be contacted first, and 2 out of 3 times, the gwdev.serv.novl host would be contacted first. Port (column 7): The port number specifies the TCP port on which the MTA listens for incoming messages. The default port number for the MTA 1s 7100. Host (column 8): The host specifies the fully-qualified host name or IP address of the MTA’s server. For a service record, you must specify the host name. For a text record, you can specify either the server’s host name or IP address. If you use a host name, it must be mapped to an IP address through an DNS "A" record. In the above example, corp.serv.novl, gwdev.serv.novl, and gwsup.serv.novl are all host names that are mapped to IP addresses through "A" records in DNS. Configuring the MTA's Server for DNS Lookups In order for an MTA in your GroupWise system to use dynamic Internet links to send messages, you must make sure the MTA’s server is properly configured for DNS lookups. Basic configuration information is provided below. Consult your DNS documentation for more detailed information about configuring a server for DNS lookups. + “Configuring a NetWare 6.x, 5.x, or 4.x Server for DNS Lookups” on page 16 + “Configuring a Windows NT Server for DNS Lookups” on page 16 + “Configuring a Windows 2000 Server for DNS Lookups” on page 16 Configuring a NetWare 6.x, 5.x, or 4.x Server for DNS Lookups On a NetWare® server, you need to have a resolv.cfg file in the sys:\etc directory that defines the DNS name server for that NetWare server. The resolv.cfg file would look similar to the following, based on a novell .com domain: domain novell.com nameserver 123.456.78.99 Consult your NetWare documentation for more detailed information about configuring a NetWare server for DNS lookups. Configuring a Windows NT Server for DNS Lookups On the Windows* NT* server: 1 Click the Start menu > Settings > Control Panel. 2 Double-click Network, then click Protocols > TCP/IP Protocol > Properties > DNS. 3 In the DNS Server Search Order box, make sure the IP address of at least one DNS name server is listed. Consult your DNS documentation for more detailed information about configuring a Windows NT server for DNS lookups. Configuring a Windows 2000 Server for DNS Lookups On the Windows 2000 server: 1 Click the Start menu > Settings > Control Panel. 16 GroupWise 6.5 Multi-System Administration Guide 2 Double-click Network and Dial-Up Connections, double-click Local Area Connection, then click Properties to display the Local Area Connection Properties dialog box. 3 In the list of protocols, select Internet Protocol (TCP/IP), then click Properties to display the Internet Protocol (TCP/IP) Properties dialog box. 4 Click Advanced to display the Advanced TCP/IP Settings dialog box. 5 Click the DNS tab, then make sure the IP address of at least one DNS name server is listed in the DNS Server Addresses list. Consult your DNS documentation for more detailed information about configuring a Windows NT workstation or server for DNS lookups. Enabling MTAs to Perform DNS Lookups After you have performed the necessary configuration to enable an MTA’s server to allow DNS lookups (see “Configuring the MTA’s Server for DNS Lookups” on page 16), you must configure the MTA to perform DNS lookups. By default, your GroupWise system is configured not to allow MTAs to perform DNS lookups. You can retain the system default of no DNS lookups, then enable DNS lookups for individual MTAs. Or you can enable DNS lookups for all MTAs in your GroupWise system, then selectively disable DNS lookups for individual MTAs. + “Enabling DNS Lookups for All MTAs” on page 17 ¢ “Enabling/Disabling DNS Lookups for Individual MTAs” on page 18 Enabling DNS Lookups for All MTAs To configure your GroupWise system so all MTAs perform DNS lookups (provided their servers are enabled for DNS lookups): 1 In ConsoleOne®, click the Tools menu > GroupWise System Operations > System Preferences to display the GroupWise System Preferences dialog box. KE Groupwise System Preferences xÍ | Default Password | Admin Lockout Settings | Routing Options | External Access Rights Set access rights automatically: C When creating a GroupWise user When creating or modifying objects, for network ID use: (° Full Distinguished Name C Common Name Cancel Help 2 Click the Routing Options tab. Using Dynamic Internet Links 17 KE Groupwise System Preferences E xÍ Nickname Settings | Default Password | Admin Lockout Settings Admin Preferences i External Access Rights Default Routing Domain: 8] Clear A For car I MTAs send directly to other GroupWise systems Cancel Help 3 Enable the Allow MTAs to Send Directly to Other GroupWise Systems option If the option is dimmed, you have not defined an Internet domain yet. See “Internet-Style Addressing” in “System” in the GroupWise 6.5 Administration Guide. 4 Click OK. Enabling/Disabling DNS Lookups for Individual MTAs If you’ve used the GroupWise System Preferences to enable all MTAs to perform DNS lookups in order to send messages directly to other GroupWise systems (see “Enabling DNS Lookups for All MTAs” on page 17), you can disable DNS lookups for individual MTAs. If you haven’t used the GroupWise System Preferences to enable all MTAs to perform DNS lookups, you can enable DNS lookups for individual MTAs. 1 In ConsoleOne, right-click the MTA object, then click Properties. 2 Click GroupWise > Routing Options to display the Routing Options page. Properties of MTA E xj "| NDS Rights + | other | Rights to Files and Folders | Override | Default Routing Domain CO A Defined at: Novell A | Fere o Defined at: Novell m [M Allow MTA f Defined at: Novell Page Options... f Cancel | App Help 3 Select the Override box to the left of the Allow MTA to Send Directly to Other GroupWise Systems option. 4 Select or deselect Allow MTA to Send Directly to Other GroupWise Systems as needed for this MTA. 5 Click OK. 18 GroupWise 6.5 Multi-System Administration Guide Understanding Dynamic Internet Links The following diagram illustrates the basic process ofestablishing a dynamic Internet link between Group Wise systems. ctp.com AI SMTP MX Mail Server Stage 1: GroupWise Client in the Sending System The GroupWise client parses the address by breaking it down into parts and attempting to map it to the userID.post_office.domain syntax. When the parsing is complete, the client looks in its own system address book and asks: "Does the parsed address match any listed in the system address book?" The address can be typed by the user or obtained from the system address book. + If Yes: The GroupWise client sends this "internal" message to the MTA to be queued for delivery. + If No: The GroupWise client attempts to resolve the address further. Go to Stage 2. Stage 2: GroupWise Client in the Sending System The GroupWise client checks the Internet domain (IDomain) addressing element listed after an @ sign in the address syntax and asks: "Is this IDomain defined in my GroupWise system (that is, is it internal)?" If there were no IDomain element at this point, the message would be undeliverable. + If Yes: The client looks at the address to determine if all parts are present. If they are present, it attempts to find a domain element in the address and resolve the address for local delivery. If a domain element cannot be found, the message is undeliverable. + If No: The client recognizes the [Domain as external to its system and queues the message to the MTA. Go to Stage 3. Using Dynamic Internet Links 19 Stage 3: GroupWise MTA in the Sending System The Group Wise MTA asks: "Does the IDomain in this address match any IDomain defined in the local Group Wise system?" + If Yes: The Group Wise MTA recognizes that the IDomain is internal and routes it to the internal domain. + If No: The Group Wise MTA cannot find a matching IDomain in its system. The Group Wise MTA attempts to find a resource to help it route the message. Go to Stage 4. Stage 4: GroupWise MTA in the Sending System The Group Wise MTA checks its system and asks: "Has a route been defined to an alternate MTA configured for IDomain service?" + If Yes: All messages with an external IDomain are routed to a designated MTA. Go to Stage 5. + IfNo: The local MTA handles messages with an external [Domain in the address. Go to Stage s Stage 5: GroupWise MTA in the Sending System The GroupWise MTA asks: "Is this system set up to support DNS lookups?" + If Yes: The GroupWise MTA checks DNS. Go to Stage 9. + If No: The GroupWise MTA attempts to find another way to connect to the IDomain. Go to Stage 6. Stage 6: GroupWise MTA in the Sending System The MTA checks the system for capability to establish SMTP links and asks: "Does this system have a designated GroupWise Internet Agent?" + If Yes: Go to Stage 7. + If No: Message is undeliverable. Stage 7: GroupWise Internet Agent in the Sending System The MTA passes the message to the designated Internet Agent in this GroupWise system. The Internet Agent checks DNS and asks: "Does DNS have a mail exchange record (MX) for this other system that I can use to establish an SMTP link?" + If Yes: The Internet Agent does a DNS lookup for an MX record. Go to Stage 8. + If No: Message is undeliverable. Stage 8: GroupWise Internet Agent in the Sending System The designated Internet Agent establishes an SMTP link with the IDomain in the address, converts the GroupWise message to SMTP format, and sends the message to the other messaging system through the SMTP Internet connection. No further information about the message is returned to the sender unless the addressee (or the addressee's mail server) replies. 20 GroupWise 6.5 Multi-System Administration Guide Stage 9: GroupWise MTA in the Sending System The MTA performs a DNS lookup at the DNS name server by asking: "Does DNS have an SRV or TXT resource record associated with this IDomain name?" + If Yes: DNS returns either a SRV or TXT resource record and returns it to the MTA. Go to Stage 10. + If No: The Group Wise MTA does not find any resource record. Go to Stage 7. Stage 10: GroupWise MTA in the Sending System The MTA reads the name-to-TCP/IP address mappings listed in the resource record for the other Group Wise system's MTAs, chooses a domain to connect to based on a priority system established in the resource record, and initiates a Group Wise Message Transport Protocol (GWMTP) connection procedure with an MTA inthe other system (sending to its port and address). Go to Stage 11. Stage 11: GroupWise MTA in the Receiving System The receiving MTA recognizes the sender's attempt to connect, then completes the GWMTP connection with the sending MTA. Go to Stage 12. Stage 12: Both GroupWise MTAs The message is sent unaltered over the GWMTP connection between the two Group Wise MTAs. Using Dynamic Internet Links 21 22 GroupWise 6.5 Multi-System Administration Guide Overview Using Direct Links When you connect two domains in different Group Wise” systems through direct links (mapped drive, UNC path, or TCP/IP connection), both systems remain external to each other, meaning that they must be administered separately. However, you can exchange information (domains, post office, users, resources, and distribution lists) so that the two systems look like one system to your Group Wise users. The following sections provide information to help you connect two systems via direct links: + + + + “Overview” on page 23 “Creating an External Domain” on page 24 “Linking to the External Domain” on page 25 “Checking the Link Status of the External Domain” on page 26 “Sending Messages Between Systems” on page 27 “Exchanging Information Between Systems” on page 27 “Message Flow Between External Domains” on page 27 For the purpose of the following discussion, GroupWise System | and GroupWise System 2 represent two separate Group Wise systems. A direct link requires an MTA in GroupWise System 1 to have access via a mapped drive or UNC path to a domain directory in GroupWise System 2, or to have a TCP/IP connection to a domain’s MTA in Group Wise System 2. Likewise, an MTA in GroupWise System 2 must have the same type of access to GroupWise System 1. To create a direct link between GroupWise System 1 and GroupWise System 2, you would do the following: + In GroupWise System 1, define one domain from Group Wise System 2 as an external domain and then configure a direct link from a domain in Group Wise System 1 to the external domain. This allows GroupWise System 1 to deliver messages to Group Wise System 2. In Group Wise System 2, define one domain from Group Wise System 1 as an external domain and then configure a direct link from a domain in Group Wise System 2 to the external domain. This allows Group Wise System 2 to deliver messages to Group Wise System 1. After you've connected the two systems, users can send messages to the other system by entering the recipients’ full addresses (userID.post_office.domain or user@host). If desired, you can simplify addressing by exchanging information between systems, which causes user information to be displayed in the Address Book. The easiest way to exchange information is to enable the External System Synchronization feature in both systems. When enabled, this synchronization constantly updates the Address Books in both systems so that local users can Using Direct Links 23 more easily address messages to and access information about the users in the external system. If you don't want to enable the External System Synchronization feature, you can manually exchange information. For information about External System Synchronization, see “External System Synchronization” in “System Operations” in “System” in the Group Wise 6.5 Administration Guide. Creating an External Domain 24 The first step in connecting two Group Wise systems via a direct link is to create an external domain in each Group Wise system. The external domain represents a domain in the other Group Wise system and provides the medium through which you define the link to the other system. 1 In ConsoleOne*, right-click Group Wise System (in the left-pane), click New > External Domain to display the Create External Group Wise Domain dialog box. Käcreate External GroupWise Domain E xÍ Domain name: Cx] Domain Database Location (optional): Cancel E Help Time Zone: XGMT-07:00) Mountain Time (US 8 Canada) X Version: E Link To Domain: I Create another domain 2 Fill in the following fields: Domain Name: Enter the name of the domain as it is defined in the external GroupWise system. Domain Database Location (Optional): This is an optional field. If you select the location of the domain database (wpdomain.db) you are connecting to, GroupWise automatically establishes a direct link to the domain, using a UNC path as the link protocol. Time Zone: Select the time zone where the domain is physically located. Version: Select the domain’s GroupWise version. The domain’s version is determined by its MTA version. The options are 4.X, 5.X, and 6. Link to Domain: Select the domain in your system that you want to link to the external domain. By default, all messages sent to the external GroupWise system will be routed to this domain. Your domain’s MTA will then route the messages to the external domain. Click OK to create the external domain. The external domain is added to your GroupWise system and is visible in the GroupWise View. In the following example, Cambridge is the external domain. GroupWise 6.5 Multi-System Administration Guide Koreli consokõne © (x File Edit View Tools Help iż Domains GroupWise View $ — Domain Name | Domain Type 5 ET ES Q Cambridge External GroupWise EJ © Cambridge Provo Primary 2 Provo Secondary @ San Jose Novell Provo ÜGWDOCISYSiprovo 4 Repeat Step 1 through Step 3 to define an external domain in the second Group Wise system. If you do not have administrative rights to that system, you will need to coordinate with that GroupWise system’s administrator. 5 Continue with the next section, Linking to the External Domain. Linking to the External Domain After you define a domain from the other Group Wise system as an external domain in your system, you need to make sure that your system’s domains have the appropriate links to the external domain. One domain in your system needs to have a direct link (mapped drive, UNC path, or TCP/IP) to the external domain. By default, this will be the domain you entered in the Link to Domain field when creating the external domain (see “Creating an External Domain” on page 24). All other domains in your system will have indirect links (through the direct link domain) to the external domain. These links are configured automatically when the external domain was created. To make sure your links are set up correctly: 1 In ConsoleOne, right-click the domain that has the direct link to the external domain, click Group Wise Utilities > Link Configuration to display the Link Configuration tool. | Clee Link Configuration Tool - \\\GWDOC\SYS\provo É A E = oj x| File Edit Search View Window Help | MM P| QA Ra oem 1 so KE Domain: Provo Outbound Links from Provo Direct: Indirect: rGateway Undefined So Cambridge % San Jose rDirect rindirect $, ? San Jose 2 In the Outbound Links list, double-click the external domain to display the Edit Domain Link dialog box. Using Direct Links 25 Lk x Description: How Provo connects to Cambridge Link Type: [piret = Cancel Settings Help Protocol: UNC v UNC Path: — [tgwisysicam Ei Scheduling. I Override Maximum send message size: fo 4 MBytes Delay message size: Em MBytes Transfer Pull Info... External Link Info... 3 Check the link configuration to make sure that the link type is Direct. 4 Select the link protocol (UNC, Mapped, or TCP/IP), then fill in the information required for the selected protocol. For more information about link types and protocols, see “Managing the Links between Domains and Post Offices” in “Domains” in the GroupWise 6.5 Administration Guide. 5 Click OK to save your changes. The external domain is displayed in the Direct column of the Outbound Links list to show that the current domain is using a direct link to the external domain. By default, the rest of the domains in your system should have an indirect link to the external domain. To verify this for a domain: 6 Inthe list of domains on the Link Configuration utility’s toolbar, select the domain whose link you want to check, then verify that the external domain is displayed in the Indirect column of the Outbound Links list. 7 After verifying your domain links, repeat Step | through Step 6 in the second GroupWise system to establish the links to the first Group Wise system. If you do not have administrative rights to that system, you will need to coordinate with that Group Wise system’s administrator. 8 Continue with the next section, Checking the Link Status of the External Domain Checking the Link Status of the External Domain 26 The GroupWise MTA has monitoring capabilities that let you determine whether the domains in your system are properly linked to the external domain. When you look at the MTA’s operation screen, you should see the external domain added to the domain count in the Status box. If the link to the external domain is closed, the MTA should be logging and displaying the reasons under its Configuration Status function. The most common reason that a direct link is closed is that the MTA cannot attach to the server or volume. There can be various reasons for a failure to attach. Make sure the server where the closed domain is located is not down. If you are using a mapped drive or UNC path for the direct link protocol, the NLM1M MTA startup file must have valid /user and /password switches to connect to the other system. If you are using the Windows NT/2000 MTA, verify the UNC path or drive mapping to the closed domain. If you are using a TCP/IP connection as the direct link protocol, the MTAs on both systems must be properly configured with the IP addresses and port numbers for the defined TCP/IP links. For more information about link protocols, see “Managing the Links between Domains and Post Offices” in “Domains” in the GroupWise 6.5 Administration Guide. GroupWise 6.5 Multi-System Administration Guide Sending Messages Between Systems Exchanging After you’ ve established links between a domain in your Group Wise system and a domain in an external Group Wise system, the MTA in your system and an MTA in the other system can route messages to the respective external systems as long as the message is addressed with a fully- qualified Group Wise address: userID.post_office.domain or user@host To simplify addressing for your Group Wise users, you can exchange information between the two systems. This enables users in your GroupWise system to use the Address Book when selecting recipients from the other system. For information, see the next section, Exchanging Information Between Systems. Information Between Systems Exchanging information between two Group Wise systems enables users in either system to use the Address Book when addressing messages to users in the other system. To exchange information, you can choose from the following methods: External System Synchronization: You can use the External System Synchronization feature to automatically exchange domain, post office, user, resource, and distribution list information between the two systems. After the initial exchange of information, any information that changes in one system is automatically propagated to the other system in order to synchronize the information in that system. This is the recommended method for exchanging information between two systems. For information about setting up synchronization between two external systems, see “External System Synchronization” in “System Operations” in “System” in the Group Wise 6.5 Administration Guide. Manual Creation of Information: You can manually create the other systems’ objects (domains, post offices, users, resources, and distribution lists) as external objects in your Group Wise system. When doing so, the names of your external objects need to exactly match the names of the objects as defined in their system. Domains in your system will link to the external domains indirectly through the first external domain you created (this is the external domain that one of your system’s domains has a direct link to). The advantage to this method is that you can choose which of the other system’s domains, post offices, users, resources, and distribution lists you want included in your system. The disadvantage is that there is a great amount of administrative overhead involved in creating all the objects and, after the objects are created, no automatic synchronization takes place so updates must be made manually. Message Flow Between External Domains Because a link to an external domain is really just a way of defining a link between a domain on your local GroupWise system and a domain on another GroupWise system, the flow of messages is identical to the flow of messages between any two GroupWise domains. For more information about message flows between domains, choose the type of link that you want to know more about in “Message Delivery to a Different Domain” in the GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. Using Direct Links 27 28 GroupWise 6.5 Multi-System Administration Guide Using Gateway Links When you can't use dynamic Internet links (see Chapter 2, “Using Dynamic Internet Links,” on page 13) or direct links (see Chapter 3, “Using Direct Links,” on page 23) to connect Group Wise” systems that are located on different networks, you can use Group Wise gateways to connect the systems. An MTA in the sending Group Wise system transfers outgoing messages to the gateway, which passes the messages to a gateway in the receiving system. The receiving gateway transfers the messages to an MTA, which then routes the messages to the appropriate post offices for delivery. The following sections present summaries of the gateway options for connecting Group Wise systems on different networks. + “Connecting Systems Through the Internet” on page 29. + “Connecting Systems Through an Asynchronous Phone Line” on page 30. + “Connecting Systems Through an X.25 Line” on page 30. + “Connecting Group Wise Systems Through Other E-Mail Systems” on page 30. GroupWise 4.1 gateways work with GroupWise 4.1, 5.x, and 6.x. Group Wise 5.x gateways work with GroupWise 5.x and 6.x. For the most current GroupWise gateway product information, contact your local Novell® office (http://www.novell.com/index/wwoffices.html). Connecting Systems Through the Internet The Internet now links thousands of networks and workstations throughout the world. GroupWise messages can pass over the Internet from one GroupWise system to another. Currently, there are two Group Wise products that let you connect Group Wise systems (and other systems) through the Internet: the GroupWise Internet Agent, and the GroupWise SMTP/MIME Gateway. GroupWise Internet Agent The Group Wise Internet Agent is used with the following GroupWise versions: + GroupWise 5.2 + GroupWise 5.5 + GroupWise 5.5 Enhancement Pack + GroupWise 6.x The GroupWise CD for each of the above versions includes the Internet Agent. You can use the Internet Agent to connect your GroupWise system to the Internet and to connect to other GroupWise systems through the Internet. For instructions about installing the Internet Agent in a Group Wise 6.5 system, see “Installing the Group Wise Internet Agent” in the GroupWise 6.5 Installation Guide. Using Gateway Links 29 For instructions about connecting GroupWise systems using the Internet Agent, see “Connecting Group Wise Systems” in “Internet Agent” in the Group Wise 6.5 Administration Guide. GroupWise SMTP/MIME Gateway The Group Wise SMTP/MIME gateway is used with the following GroupWise versions: + GroupWise 4.1 + Group Wise 5.0 + Group Wise 5.1 For information about obtaining the SMTP/MIME gateway for use with the Group Wise versions, contact your local Novell office (http://www.novell.com/index/wwoffices.html). Connecting Systems Through an Asynchronous Phone Line Another common way to connect Group Wise systems on different networks is across phone lines, either through dedicated lines or by using modems for more occasional access. The Group Wise Async Gateway provides this capability. For more information, see the GroupWise Async Gateway Guide at the GroupWise 6.x Gateways Web site (http://www.novell.com/documentation/ gw6xgate). Connecting Systems Through an X.25 Line X.25 lines can also be used to connect Group Wise systems on different networks. The Group Wise X.25 gateway provides this capability. For more information, see the Group Wise X.25 Gateway Guide at the Group Wise 6.x Gateways Web site (http://www.novell.com/documentation/gw65). Connecting GroupWise Systems Through Other E-Mail Systems Several Group Wise gateways allow Group Wise messages to pass through other e-mail systems with no loss of Group Wise functionality. This setup is termed "passthrough" or "tunneled" messaging. Group Wise messages are encapsulated into the format of the other e-mail system and sent to the Group Wise system on the other end. No Group Wise functionality is lost. This is a convenience when the other e-mail system is already configured to connect sites where Group Wise is also in use. The gateways that can be used for passthrough messaging include: + GroupWise 5.x/6.x Internet Agent + GroupWise 4.1/5.0/5.1 SMTP/MIME Gateway + GroupWise Gateway for Microsoft* Mail + GroupWise Gateway for Lotus* Notes* * GroupWise Gateway for Lotus cc:Mail* + GroupWise Gateway for Office Vision/VM* + GroupWise X.400 Gateway + GroupWise SNADS Gateway For information about these gateways, see the GroupWise gateway guides at the GroupWise 6.5 documentation Web site (http://www.novell.com/documentation/gw65). 30 GroupWise 6.5 Multi-System Administration Guide Connecting to Non-GroupWise Messaging Systems Chapter 5, “GroupWise Internet Agent,” on page 33 Chapter 6, “GroupWise Gateways,” on page 35 Connecting to Non-GroupWise Messaging Systems 31 32 GroupWise 6.5 Multi-System Administration Guide GroupWise Internet Agent The preferred way to connect to non-Group Wise messaging systems is through the Internet. Group Wise” provides connectivity to the Internet through the Group Wise Internet Agent. The Internet Agent uses standard Internet protocols and formats. This means that messages can be sent to or received from any Internet-connected e-mail system that can handle MIME or RFC-822 formatted messages sent using the SMTP protocol. The Internet Agent also supports POP3 and IMAP4, which means that POP3/IMAP4 clients can be used to access Group Wise mailboxes. In addition, the Internet Agent supports LDAP, which means that it can act as an LDAP server by providing LDAP queries of the Group Wise directory. For information about installing the Internet Agent, see “Installing the Group Wise Internet Agent” in the GroupWise 6.5 Installation Guide. For information about configuring and administering the Internet Agent, see “Internet Agent” in the GroupWise 6.5 Administration Guide. GroupWise Internet Agent 33 34 GroupWise 6.5 Multi-System Administration Guide GroupWise Gateways Group Wise” provides gateways to enable you to connect directly to a variety of messaging systems, message transport protocols, and communication standards. For example, GroupWise provides gateways for the Microsoft Exchange and Lotus Notes messaging systems as well as the X.400 message transport protocol. For up-to-date information about currently available GroupWise gateways, see the GroupWise Gateways Web site (http://www.novell.com/products/groupwise/gateways/details.html). GroupWise Gateways 35 36 GroupWise 6.5 Multi-System Administration Guide Merging with GroupWise 5.x and 6.x Systems This section helps you merge another GroupWise? 5.x or 6.x system into your Group Wise 6.x system. Chapter 7, “Why Merge Group Wise Systems?,” on page 39 Chapter 8, “Planning the Merge,” on page 41 Chapter 9, “Preparing for the Merge,” on page 53 Chapter 10, “Merging the Group Wise Systems,” on page 55 Merging with GroupWise 5.x and 6.x Systems 37 38 GroupWise 6.5 Multi-System Administration Guide Why Merge GroupWise Systems? If you are consolidating organizations or combining departments, you might want to merge two or more GroupWise® 5.x or 6.x systems rather than connect them (see “Connecting to Group Wise 5.x and 6.x Systems” on page 9). WARNING: When merging systems, do not merge a domain from one system into another system if the merged domain is a newer version than the primary domain of its new system. For example, do not merge a GroupWise 6 domain into a GroupWise system whose primary domain is version 5.5. The primary domain in a GroupWise system must always be at or above the version level of all secondary domains in the system. You can achieve the same GroupWise functionality for your users by merging systems or by connecting them. Therefore, the question of whether to merge GroupWise systems is mostly a matter of administration: + If you want your entire GroupWise system configured so it can be administered by one administrator from any location without needing to change system connections and manage external objects, you should merge your systems. ¢ Ifyou want your entire GroupWise system configured so it can be administered by any administrator from any location, and changing system connections and managing external objects are not issues, you do not need to merge the systems. ¢ Ifyou want independent administrators for each GroupWise system, whether the systems are connected or not, you should not merge the systems. If you want to merge a GroupWise 5.x or 6.x system into your Group Wise 6.x system, continue with Chapter 8, “Planning the Merge,” on page 41. If you do not want to merge the systems, but they are not connected and you would like to have them connected, see “Connecting to GroupWise 5.x and 6.x Systems” on page 9. Why Merge GroupWise Systems? 39 40 GroupWise 6.5 Multi-System Administration Guide Planning the Merge The “Merge Planning Worksheet” on page 49 lists all the information you will need as you merge a Group Wise” 5.x or 6.x system into your Group Wise 6.x system. When you have completed the following planning tasks and filled out the worksheet, you will be ready to continue with Chapter 9, “Preparing for the Merge,” on page 53. + “Understanding the Merge Process” on page 41 + “Planning Administrator Rights” on page 43 + “Determining Which Group Wise Objects Are No Longer In Use” on page 43 + “Planning the Location of the Domain Database Backup Directories” on page 43 + “Planning GroupWise System Connections” on page 44 + “Planning to Merge Additional GroupWise Systems” on page 47 + “Merge Planning Worksheet” on page 49 Understanding the Merge Process A merge is performed between the primary domains of two GroupWise systems. Merging one system (the primary domain and all of its subordinate objects) with another consolidates the two systems, resulting in only one primary domain and one or more new secondary domains and their subordinate objects. To avoid confusion, we will hereafter refer to the system whose primary domain you’ lI retain as Site #1 and the other system as Site #2. GroupWise Systems to be Merged MANHATTAN LAKEWOOD GroupWise System-Site #1 GroupWise System-Site #2 Headquarters Branch1 Primary Domain Primary Domain Research | Accounting Distribution Secondary Secondary Secondary Domain Domain Domain | In the above illustration, we have two GroupWise systems that are not connected. We have designated the Manhattan GroupWise system as Site #1 and the Lakewood GroupWise system as Site #2. The Lakewood system will be merged into the Manhattan system. Planning the Merge 41 42 If you have three or more systems to be merged, you must merge the systems one after the other. We will not use references to a Site #3, a Site #4, and so on. Instead, after the first and second systems have been merged, the third system will become Site #2 as you go through the merge planning, preparation, and step sections again. Therefore, each system will take its turn at being Site #2 while the first system being merged to will continue to be Site #1. The merge process permanently affects a database. Before merging you will create backups of all wpdomain.db files for the primary and secondary domains that will be affected by the merge. This will allow you to recover from any mistakes. For more information, see “Planning the Location of the Domain Database Backup Directories” on page 43. During the merge, you must shut down any Group Wise Message Transfer Agents (MTAs) that can write to the domain databases. Even though you will shut down the MTAs during the merge, users can continue to use GroupWise because the Post Office Agents (POAs) do not need to be shut down. The following Group Wise agent functions will not be available until the MTAs are running again: ¢ Transferring e-mail messages between post offices + Logging statistics + Updating domain database files + Replicating database information + Synchronizing GroupWise with Novell® eDirectory™ + Repairing domain databases Print a copy of the Merge Planning Worksheet. WORKSHEET Under Item 23: GroupWise MTAs for Sites #1 and #2, list the GroupWise MTAs for both sites that you will need to shut down during the merge. The items in the worksheet are listed in the order you will enter them when running the GroupWise merge utility. This planning section does not follow the same order as the worksheet, but all worksheet items are covered. If Site #2 has a primary domain and some secondary domains, you will first release all of the secondary domains in Site #2 to become primary domains in their own GroupWise systems. Then you will merge each Site #2 primary domain one at a time with the primary domain of Site #1. In other words, you will be running the merge process once for each domain in Site #2. For more information, see “Releasing Site #2 Secondary Domains” on page 59. One link (of any type) must exist between a domain in Site #1 and the domain being merged in Site #2. The merge utility automatically creates indirect links between the Site #1 secondary domains and the Site #2 domain being merged. You have the option to accept these indirect links and configure them later (if necessary), or you can create direct links between all domains in Site #1 and the domain being merged from Site #2 before beginning the merge. All links must be completed and correct before you run the MTAs after merging the systems. For more information, see “Linking the Domains” on page 46. GroupWise 6.5 Multi-System Administration Guide WORKSHEET Under Item 16: Site #1 Name, enter the name of the GroupWise system you will designate as Site #1. Under Item 7: Site #2 Name, enter the name of the GroupWise system you will designate as Site #2. If you are merging three or more GroupWise systems, you will be selecting a different system as Site #2 each time you reuse this planning section and rerun the merge process. Under Item 14: Site #1 Primary Domain, enter the exact name of your Site #1 primary domain. Under Item 5: Site #2 Primary Domain, enter the exact name of your Site #2 primary domain. Under Item 18: Site #1 Secondary Domains, enter the exact names of your Site #1 secondary domains. Under Item 10: Site #2 Secondary Domains, enter the exact names of your Site #2 secondary domains. Under Item 17: Site #1 Time Zone, enter the time zone for Site #1. Under Item 9: Site #2 Time Zone, enter the time zone for Site #2. Planning Administrator Rights To perform the merge process, the Site #1 administrator needs to have exclusive access to the Site #2 databases. This access can be to either the Site #2 domain databases if the two GroupWise systems are connected, or to copies of the Site #2 domain databases if the systems are not connected. Exclusive access is created when the GroupWise MTAs are shut down and the administrator has admin-equivalent rights to the two systems. See “Group Wise Administrator Rights” in “Security” in the GroupWise 6.5 Administration Guide for information on setting up administrator rights. WORKSHEET If the administrator performing the merge has the necessary rights, under Item 2: Does Administrator Performing the Merge Have Admin-Equivalent Rights to Both Systems?, select Yes or No. Determining Which GroupWise Objects Are No Longer In Use You can save merging time and end up with a less cluttered GroupWise system if you determine which Group Wise objects in Site #2 are no longer used and remove them. You can also use this opportunity to delete any eDirectory user objects that are no longer used. WORKSHEET Under Item 3: GroupWise Objects to Delete, list each eDirectory user, GroupWise user account, resource, and distribution list that you want to delete. Planning the Location of the Domain Database Backup Directories Because the domain database is critical to the performance of GroupWise, you should always create a backup copy of the domain databases you will be manipulating. This ensures that an original version of each database is available should you make a mistake, or if any problems should Planning the Merge 43 arise during the merge process. You can always return to the former configurations while you correct any problems encountered. WORKSHEET Under Item 15: Paths to Site #1 WPDOMAIN.DBs, enter paths to the Site #1 WPDOMAIN.DB files. Under Item 6: Paths to Site #2 WWPDOMAIN.DBs, enter paths to the Site #2 WPDOMAIN.DB files. Under Item 24: Paths to Site #1 Backup Directories, enter the path to the backup directory you will create to hold the backup copy of the Site #1 domain database. Under Item 25: Paths to Site #2 Backup Directories, enter the path to each backup directory you will create to hold the backup copy of a Site #2 domain database. Every domain database has the same name, so plan to either temporarily rename the database copies or to create separate directories for them. Planning GroupWise System Connections 44 The merge cannot occur unless Site #1 is able to make a direct connection to the Site #2 domain being merged. You should have direct system connections established between Site #1 and Site #2 so that you can open the databases. If you are able to connect to Site #2 and have appropriate rights, you can create external domains, release secondary domains, and merge domains in the Group Wise View. If you cannot open the domain databases to be merged (you do not have the necessary rights and/ or the systems cannot be connected), you will need to use copies of each Site #2 domain database for making the direct connections. So that the database copies will accurately mirror the live databases, you and the other GroupWise administrator involved with the merge should avoid making any administrative changes in Group Wise after you have made the copies of the Site #2 databases. Group Wise clients can function in the two systems while you run the merge against the copy. If you are the Site #1 administrator, you will create directories for the Site #2 database copies (both the original Site #2 primary domain and the newly-released Site #2 domain databases). During the merge process, you will need to target each of these directories to merge that domain to the Site #1 system. When the merge process is completed, you will copy the merged database copies over the live databases. If you want to merge systems that are connected through a GroupWise gateway, you should treat the systems as if they are not connected. This is because the merge requires use of external domains. WORKSHEET If the GroupWise systems you are merging are already connected, select Yes under Item 4: Systems Connected?; otherwise, select No. If you selected No for worksheet item 4 and the systems cannot be connected, enter the path to each temporary directory you must create to hold the copies of the Site #2 wpdomain.db files under Item 21: Paths to Site #2 Temporary Holding Directories. If you selected No for worksheet item 4 and the temporary directories you create for the Site #2 domain copies are on another tree, select Yes under Item 22: Temporary Directories for Site #2 on Another Tree?; otherwise, select No. If you select Yes, you will need to be logged in to the other tree during the merge. GroupWise 6.5 Multi-System Administration Guide External Domains Ifthe GroupWise systems you are merging are not already connected through external domains, you will need to create external domains to connect the systems. An external domain, which you must create manually, provides a reference in your Group Wise system from which you can add a link to another Group Wise system. You will need external domains in each system with names that are identical to the domain names of the site with which the merge is planned. You will also need a link between the two systems. GroupWise Systems with External Domains Defined MANHATTAN LAKEWOOD GroupWise System-Site #1 GroupWise System-Site #2 Headquarters Branch1 Primary Domain kt Primary Domain Headguarters Extemal Domain Research Accounting |Distribution| | Branch1 Distribution Secondary Secondary External Extemal Secondary Domain Domain Domain Domain Domain In the above illustration, we have created external domains in each system to represent where we will need direct connections for performing the merge. You must have rights to Site #2 (that is, you must be able to authenticate to its servers) so that you can establish a system connection using the Group Wise View. If you are able to connect to Site #2, you can create external domains in that system. For more information, see “Planning Administrator Rights” on page 43. Creating a Site #2 external domain in Site #1 does not add an object to your eDirectory tree; however, you will be able to see the external domain object in the Group Wise View. A reference to the external domain is added to your own system’s databases so that it can use the defined link to route messages to users represented in the external domain. WORKSHEET Under Item 13: Site #1 External Domain Names, enter the exact name of each Site #1 domain you want to create as an external domain in Site #2. Refer to worksheet items 14 and 18 for the Site #1 domain names. Under Item 19: Descriptions for Site #1 External Domains, enter descriptions for the Site #1 external domains. Under Item 8: Site #2 External Domain Names, enter the exact name of each Site #2 domain you must create as an external domain in Site #1. Refer to worksheet items 5 and 10 for the Site #2 domain names. Under Item 11: Descriptions for Site #2 External Domains, enter descriptions for the Site #2 external domains. Planning the Merge 45 Linking the Domains It is important that the inbound links for the external domains you create in Site #2 and Site #1 are established and correct for both systems. These links are used to transfer messages, including administrative messages, from one Group Wise system to another. Each domain object in eDirectory includes a link configuration attribute that is used to control access to link information. If you have appropriate eDirectory rights, you can view the domain links with the Link Configuration tool available in ConsoleOne*. You can create links (of any type) between the domain being merged from Site #2 and the secondary domains in Site #1 before running the merge. However, this is not necessary to perform the merge. Instead, you can allow the merge utility to automatically create the indirect links between the secondary domains of Site #1 and the domain being merged from Site #2, and you can later optimize your system by reconfiguring the indirect links created by the merge utility. WORKSHEET If you want the merge utility to automatically create indirect links between the Site #2 domain being merged and the secondary domains in Site #1, select Yes under Item 12: Allow Indirect Links to Site #1 Secondary Domains?; otherwise, select No so that you can configure the links before performing the merge. If you selected Yes for worksheet item 12, edit your domains list under Item 13: Site #1 External Domain Names to indicate which one Site #1 domain will be linked to the Site #2 domain being merged. See “Managing the Links between Domains and Post Offices” in “Domains” in the GroupWise 6.5 Administration Guide for information on setting up direct links between domains. WORKSHEET Under Item 20: Link Configuration Fields, enter the information needed for the following link configuration fields for each direct link you will create: Description: Indicate which domains are being directly linked. Link Type: Select Direct as the type of link between the domains. Settings - Protocol: Select UNC as the protocol for communication between the domains. Settings - Path or UNC Path: Enter the UNC path to the domain being merged. Releasing the Secondary Domains in Site #2 46 You will release GroupWise secondary domain databases in Site #2 before you merge them into Site #1. A released domain database is one that you disassociate from a primary domain. In effect, each released domain (which shows as an external domain for Site #1) is its own, independent system. GroupWise 6.5 Multi-System Administration Guide GroupWise Systems with Site #2 Secondary Domain Released MANHATTAN LAKEWOOD GroupWise System-Site 41 GroupWise System-Site #2 Headquarters Branch1 Distribution Primary Domain Primary Domain Primary Domain e Research | Accounting) |Distribution| | Branch1 Headguarters Headguarters Secondary Secondary External Extemal External External Domain Domain Domain Domain Domain Domain In the above illustration, the secondary domain in the Lakewood system has been released to become its own primary domain. Each primary domain in the Lakewood system maintains a direct connection with the Headquarters domain in Site #1 through the Headquarters external domain created earlier for the Lakewood system. Releasing a secondary domain requires the system to use drive mappings or UNC paths to locate the domains to be released. If you have established a system connection to Site #2 through your network, you can release a Site #2 secondary domain in the GroupWise View. When you release a secondary domain, it becomes an external Site #2 domain and is considered a primary-level domain in its own single-domain system. The released (that is, external) domain can then be merged into Site #1 to become a secondary domain there. If the systems are not connected (worksheet item 4), the Site #2 GroupWise administrator must have network access to the temporary holding directories where you copied the wpdomain.db files for the Site #2 primary and secondary domains. You will need to establish a system connection to the temporary directory where you copied the Site #2 primary domain database before you can release a Site #2 secondary domain. Planning to Merge Additional GroupWise Systems If you have three or more systems to be merged, you must merge the systems one after the other. We will not use references to Site #3, Site #4, and so on. Instead, after the first and second systems have been merged, the third system will become Site #2 as you go through the merge planning, preparation, and step sections again. Therefore, each system will take its turn at being Site #2 while the first system being merged to will continue to be Site #1. WORKSHEET If you are merging three or more GroupWise systems, select Yes and continue in this section under Item 1: Merging Three or More GroupWise Systems?; otherwise, select No and you are finished with your planning. If you have three or more GroupWise systems to be merged, you can merge them in one session or at different times. In either case, you will be merging them one after the other with each additional system taking a turn at being Site #2. You will need a separate worksheet for each additional system being merged. Whether you merge the systems in one session or at different times, you will probably be able to copy information specific to Site #1 to each additional worksheet, because most of that information should not be changed by a merge. Planning the Merge 47 The merge process can be very lengthy when three or more systems are merged, especially if each system being merged has a number of secondary domains. For example, when you merge several systems, you select one as Site #1. This first system will retain its primary domain, while the primary and secondary domains of the other systems will all become secondary domains in Site #1. Also, all secondary domains in the other systems will each need to be released before they can be merged. Since the merge process itself involves moving only one domain at a time, you could be running the release and merge programs many times—once for each primary and secondary domain in the second system, then the third system, and so on. Merging in One Session If you plan to merge all of your GroupWise systems in one session, you will want to fill out all of the worksheets before running the merge utility. Therefore, as you fill out the worksheets for each system, keep in mind the changes in structure for Site #1 that will occur after each system is merged with it. Print another copy of the Merge Planning Worksheet for each additional Group Wise system to be merged. WORKSHEET Do the following on each additional worksheet. Under Item 16: Site #1 Name, enter the name of the GroupWise system you will designate as Site #1. Under Item 7: Site #2 Name, enter the name of the GroupWise system you will designate as Site #2. If you are merging three or more GroupWise systems, you will be selecting a different system as Site #2 each time you reuse this planning chapter and rerun the merge process. Under Item 23: GroupWise MTAs for Sites #1 and #2, list the GroupWise MTAs that you will need to shut down during the merge. Because you should be including all domains in the previously combined systems, your list should be longer for each subsequent worksheet. Merging at Different Times 48 You might not want to merge several systems in one session. The amount of time required depends on how many secondary domains exist in each additional system. This is because you must release and merge each secondary domain one at a time. If you plan to merge your Group Wise systems at different times, you can fill in each additional worksheet when you are ready to plan the merge for its system using this section. GroupWise 6.5 Multi-System Administration Guide Merge Planning Worksheet The Group Wise Merge Domain Advisor helps you merge GroupWise systems. You need to prepare for the merge by planning the location and structure of your domain databases. Item 1) Merging Three or More GroupWise Systems? + Yes + No 2) Does Administrator Performing the Merge Have Admin-Equivalent Rights to Both Systems? + Yes + No 3) GroupWise Objects to Delete: 4) Systems Connected? + Yes + No 5) Site #2 Primary Domain: 6) Paths to Site #2 Wpdomain.db Files: 7) Site #2 Name: Example No Yes None No Branch1 \\gw\sys\branch1 \\gw\sys\distrib Lakewood Explanation If you will be merging three or more GroupWise systems, whether in one session or at different times, select Yes; otherwise, select No. For more information, see “Understanding the Merge Process” on page 41. If the administrator does not have the necessary rights to perform the merge, select No; otherwise, select Yes. The merge utility depends on the rights of the person logged in for access to the applicable databases. For more information, see “Planning Administrator Rights” on page 43. List any eDirectory user objects, GroupWise user accounts, resources, or distribution lists that are no longer in use. Enter "none" if you have nothing to delete. For more information, see “Determining Which GroupWise Objects Are No Longer In Use” on page 43. If the GroupWise systems you are merging are not connected, select No; otherwise, select Yes. For more information, see “Planning GroupWise System Connections” on page 44. List the name of the primary domain for Site #2. For more information, see “Understanding the Merge Process” on page 41. To merge a domain from Site #2, you must supply the path to the wpdomain.db file for the domain being merged. If there are multiple domains in Site #2, list the paths for each wpdomain.db file. For more information, see “Planning the Location of the Domain Database Backup Directories” on page 43. Identify the GroupWise system you want to merge into Site #1. The primary domain of this system will become a secondary domain in Site #1. Each secondary domain in Site #2 will be released so it can be merged as a primary domain. For more information, see “Understanding the Merge Process” on page 41. Planning the Merge 49 Item 8) Site #2 External Domain Names: 9) Site #2 Time Zone: 10) Site #2 Secondary Domains: 11) Descriptions for Site #2 External Domains: 12) Allow Indirect Links to Site #1 Secondary Domains? + Yes + No 13) Site #1 External Domain Names: 50 GroupWise 6.5 Multi-System Administration Guide Example Headquarters Central Distribution Headquarters - primary Yes Branch1 Distribution Explanation There must be at least one direct link between a domain in Site #1 and each domain being merged from Site #2. Specify the exact name of the external domains you will create in Site #2. Each external domain you create in Site #2 must correspond to a domain of the same name in Site #1. If you selected Yes for worksheet item 12, you only need to create one external domain in Site #2 because indirect links will automatically be created between the other domains in Site #1 and the domain being merged from Site #2. If you selected No for worksheet item 12, you need to create direct links from all primary and secondary domains in Site #1 to Site #2, and from all primary and secondary domains in Site #2 to Site #1. For more information, see “External Domains” on page 45. Enter the local time zone for Site #2. For more information, see “Understanding the Merge Process” on page 41. List the names of all secondary domains in Site #2. One at a time, each secondary domain in Site #2 will be released to become an independent primary domain on its own to be merged into Site #1. For more information, see “Understanding the Merge Process” on page 41. Enter an informative description for each Site #2 external domain. For more information, see “External Domains” on page 45. Select Yes and the merge utility will automatically create indirect links between the secondary domains in Site #1 and the domain being merged from Site #2. You can configure links later, if necessary. Select No if you want to configure all of your links before performing the merge. For more information, see “Linking the Domains” on page 46. You must have an external domain in Site #1 for each primary and secondary domain in Site #2. Specify the exact name of each external domain you will create in Site #1 that corresponds to a domain of the same name in Site #2. For more information, see “External Domains” on page 45. Item 14) Site #1 Primary Domain: 15) Paths to Site #1 Wpdomain.db Files: 16) Site #1 Name: 17) Site #1 Time Zone: 18) Site #1 Secondary Domains: 19) Descriptions for Site #1 External Domains: 20) Link Configuration Fields: + Description: + Link Type: + Settings - Protocol: + Settings: Path or UNC Path: Example Headquarters \\gw\sys\headq Manhattan Eastern None Branch1 - primary Distribution - secondary Headquarters Direct UNC \\gw\sys\headq (This example is only for a Headquarters link. You will need to list this information for each link.) Explanation List the name of the primary domain for Site #1. For more information, see “Understanding the Merge Process” on page 41. If you selected Yes for worksheet item 12, you will make a direct link only to the primary domain of Site #1. List the path to its wpdomain.db file. If you selected No for worksheet item 12, you will need to make direct links to all Site #1 secondary domains. List each of the paths to their wpdomain.db files. For more information, see “Planning the Location of the Domain Database Backup Directories” on page 43. Identify the GroupWise system you want to be Site #1. This system will retain its primary domain status. For more information, see “Understanding the Merge Process” on page 41. Enter the local time zone for Site #1. For more information, see “Understanding the Merge Process” on page 41. If you selected No for worksheet item 12, you will be creating direct links between the secondary domains in Site #1 and the domains being merged from Site #2. List the Site #1 secondary domains. If you selected Yes for worksheet item 12, enter "none" because indirect links will automatically be made by the merge utility to secondary domains in Site #1. For more information, see “Understanding the Merge Process” on page 41. Enter an informative description for each Site #1 external domain. For more information, see “External Domains” on page 45. Fill in the fields once for each link being set up. For more information, see “Linking the Domains” on page 46. Planning the Merge 51 Item 21) Paths to Site #2 Temporary Holding Directories: 22) Are Temporary Holding Directories for Site #2 on Another Tree? + Yes + No 23) GroupWise MTAs for Sites #1 and #2: 24) Paths to Site #1 Backup Directories: 25) Paths to Site #2 Backup Directories: Example \\gw\sys\hold\branch1 \\gw\sys\hold\distrib No MTA.Headquarters. Manhattan MTA.Research.Manhattan MTA.Accounting.Manhattan MTA.Branch1.Lakewood MTA. Distribution.Lakewood \\gw\sys\bak\research \\gw\sys\bak\headq \\gw\sys\bak\account \\gw\sys\bak\distrib \\gw\sys\bak\branch1 52 GroupWise 6.5 Multi-System Administration Guide Explanation If the systems you are merging cannot be connected, and you are the administrator for Site #1, specify the paths for each temporary holding directory you will create to hold the domain databases of Site #2. Name the directories so that you can keep track of which domain the database file belongs to. For more information, see “Planning GroupWise System Connections” on page 44. If your temporary holding directories are located on a tree different than the one Site #1 is on, select Yes; otherwise, select No. If you select Yes, you will need to be logged in to the other tree during the merge. For more information, see “Planning GroupWise System Connections” on page 44. The MTAs must be shut down during the merge to prevent changes from being made to the domain databases. The POAs can be left running so that users can use GroupWise during the merge. Enter the applicable MTAs for both systems. For more information, see “Understanding the Merge Process” on page 41. To protect against losing information in case of error, you need a backup of each Site #1 domain database. You should place each wpdomain.db file in a separate backup directory. Enter the paths for each directory. For more information, see “Planning the Location of the Domain Database Backup Directories” on page 43. To protect against losing information in case of error, you need a backup of each Site #2 domain database. You should place each wpdomain.db file in a separate backup directory. Enter the paths for each directory. For more information, see “Planning the Location of the Domain Database Backup Directories” on page 43. Preparing for the Merge Before you merge two Group Wise” systems, you need to prepare the Group Wise systems. The “Merge Planning Worksheet” on page 49 contains information you will need to prepare for the merge. Do the following tasks to prepare the Group Wise domains for merging. + “Setting Up Administrator Rights” on page 53 + “Deleting Unused Group Wise Objects” on page 53 + “Verifying That UNC Paths Are Correct” on page 53 + “Resolving Pending Operations” on page 54 Setting Up Administrator Rights Make sure the administrator performing the move is an admin-equivalent in Novell® eDirectory™ (worksheet item 2). Make sure the administrator also has access to the GroupWise systems being merged. See “Group Wise Administrator Rights” in “Security” the GroupWise 6.5 Administration Guide for information on setting up administrator rights. Deleting Unused GroupWise Objects Use ConsoleOne® and the Group Wise View to delete any eDirectory User objects, GroupWise user accounts, and GroupWise distributions lists that are no longer in use (worksheet item 3). Verifying That UNC Paths Are Correct Merging GroupWise systems requires the use of correct UNC paths. The merge will bring over all UNC paths defined for Site #2. Even if you have already defined UNC paths, verify that they are accurate. See the following worksheet items for the paths you will be using: + Item 6: Paths to Site #2 Wpdomain.db Files + Item 15: Paths to Site #1 Wpdomain.db Files + Item 21: Paths to Site #2 Temporary Holding Directories + Item 24: Paths to Site #1 Backup Directories + Item 25: Paths to Site #2 Backup Directories Preparing for the Merge 53 Resolving Pending Operations When you release secondary domains in Site #2, you will be asked to resolve any pending operations. You can speed up the release operations by doing this now. 1 In ConsoleOne, make sure you are connected to the Group Wise system for Site #2, then click Tools > Group Wise System Operations > Pending Operations. 2 Note any pending operations and resolve them. 54 GroupWise 6.5 Multi-System Administration Guide Merging the GroupWise Systems The information in this section will help you to merge Site #2 into Site #1. The Merge Planning Worksheet contains all the information the merge process will prompt you for. (If you have several worksheets because you are merging three or more systems, you will only use one worksheet each time you follow the steps in this chapter.) Some tasks apply only to systems that cannot be directly connected. If you selected Yes for worksheet item 1, be sure you are using the worksheet for the GroupWise® system being merged. Do the following tasks to merge Site #2 into Site #1. + “Creating External Domains for Both Systems” on page 55 + “Configuring Links Between Site #2 Domains and Site #1 Secondary Domains” on page 57 + “Checking Links to External Domains for Both Systems” on page 57 + “Creating Temporary Holding Directories” on page 58 + “Releasing Site #2 Secondary Domains” on page 59 + “Sending Site #2 Databases to the Site #1 Administrator” on page 60 + “Receiving Site #2 Databases at Site #1” on page 60 + “Merging a Site #2 Domain into Site #1” on page 60 + “Merging the Next GroupWise System” on page 61 + “Sending the Merged Site #2 Databases to Site #2” on page 61 + “Restarting the GroupWise Agents” on page 61 + “Testing the Merged System” on page 62 Creating External Domains for Both Systems This section applies only if the systems you are merging are not already connected through external domains (worksheet item 4). Both the Site #1 and Site #2 administrators must create an external domain to represent the domain structure in the corresponding system. In other words, if you are the Site #1 administrator, you will create Site #2 external domains in your system to represent the domains in Site #2. If you are the Site #2 administrator, you will create Site #1 external domains in your system to represent the domains in Site #1. Refer to the appropriate section for instructions: + “Creating Site #1 External Domains in Site #2” on page 56 + “Creating Site #2 External Domains in Site #1” on page 56 Merging the GroupWise Systems 55 Creating Site #1 External Domains in Site #2 1 In ConsoleOne®, make sure you are connected to the Site #2 Group Wise system (worksheet item 7). 2 Right-click GroupWise System in the Group Wise View, then click New > External Domain to display the Create External GroupWise Domain dialog box. ‘a Käcreate External Group Wise Domain E x Domain name: Cx] Domain Database Location (optional): Cancel = Help i xl Time Zone: fomr-o7 00) Mountain Time (US 8 Canada) Version: [6 E Link To Domain: Prova = [> Create another domain 3 Fill in the fields: Domain Name: Enter the name of the Site #1 domain you are connecting to (worksheet item 8). This creates the external domain on Site #2. Names are not case-sensitive. Domain Database Location: Select the path to the Site #1 domain database (wpdomain.db) you will link to. ConsoleOne interprets a mapped location as a UNC path (worksheet item 6). Time Zone: Select the time zone where the Site #1 domain is physically located (worksheet item 9). Version: Select the database version for the Site #1 domain. The version is determined by the domain’s MTA version. Link to Domain: Select the domain in Site #2 you want the external domain to link to. ConsoleOne creates a direct link to this domain (worksheet item 5 and worksheet item 10). 4 Click Create to create the external domain and add it to the GroupWise View. 5 Repeat Step 2 through Step 4 for every Site #1 external domain you need to create (worksheet item 12 and worksheet item 13). Creating Site #2 External Domains in Site #1 56 You must also create a Site #2 external domain in Site #1. 1 In ConsoleOne, make sure you are connected to the Site #1 GroupWise system (worksheet item 14 and worksheet item 15). 2 Right-click GroupWise System in the GroupWise View, then click New > External Domain to display the Create External GroupWise Domain dialog box. GroupWise 6.5 Multi-System Administration Guide Käcreate External GroupWise Domain Domain name: x Domain Database Location (optional): Cancel j= Help Time Zone: [(omr-07:00) Mountain Time (US 8 Canada) zl Version: fe H Link To Domain: [Provo xj I Create another domain 3 Fill in the fields: Domain Name: Enter the name of the Site #2 domain you are connecting to (worksheet item 5 and worksheet item 10). Names are not case sensitive. Domain Database Location: Select the path to the Site #2 domain database (wpdomain.db) you are connecting to. ConsoleOne will interpret a mapped location as a UNC path (worksheet item 15). Time Zone: Select the time zone where the external domain is physically located (worksheet item 17). Version: Select the database version for the Site #2 domain. The version is determined by the domain’s MTA version. Link to Domain: Select the domain in your system you want the external domain linked to. The MTA for the Site #1 domain you specify will route messages to and from the external domain (worksheet item 14 and worksheet item 18). Click Create to create the external domain and add it to the GroupWise View. Repeat Step 2 through Step 4 for every Site #2 external domain you need to create (worksheet item 5 and worksheet item 10). Configuring Links Between Site #2 Domains and Site #1 Secondary Domains If you selected No under worksheet item 12, configure the links between each Site #2 domain and all of the secondary domains in Site #1 (worksheet item 13). See “Managing the Links between Domains and Post Offices” in “Domains” in the GroupWise 6.5 Administration Guide for information on setting up direct links between domains. Checking Links to External Domains for Both Systems The merge cannot be performed if there are broken or missing links. Therefore, you should check the links in Site #1 and check the links in Site #2. Refer to the appropriate section for instructions: + “Checking Links to Site #1 External Domains in Site #2” on page 58 + “Checking Links to Site #2 External Domains in Site #1” on page 58 Merging the GroupWise Systems 57 Checking Links to Site #1 External Domains in Site #2 You will use the Link Configuration tool to verify that each Site #1 primary domain or a Site #1 secondary domain has an inbound link from the Site #2 external domain. 1 In ConsoleOne, make sure you are connected to the Site #2 Group Wise system. 2 Click the Tools menu > Group Wise Utilities > Link Configuration to launch the Link Configuration tool. 3 Inthe domain list, select the external domain (worksheet item 13) whose inbound links you want to check. 4 Check the Inbound Links window (displayed by default for an external domain) to make sure that a direct link icon labeled with a Site #2 secondary or primary domain name is displayed there (worksheet item 8). An inbound link to the Site #1 external domain from a Site #2 domain is required for the merge to proceed. 5 If the link is incorrectly configured, double-click the Site #2 domain name to display the Edit Domain Link dialog box. 6 Edit the fields as necessary (worksheet item 20), then click OK to save your changes. Checking Links to Site #2 External Domains in Site #1 You will use the Link Configuration tool to verify that each Site #2 external domain has an inbound link from either the Site #1 primary domain or a Site #1 secondary domain. 1 In ConsoleOne, make sure you are connected to the Site #2 GroupWise system. 2 Click the Tools menu > GroupWise Utilities > Link Configuration to launch the Link Configuration tool. 3 In the domain list, select the external domain (worksheet item 8) whose inbound links you want to check. 4 Check the Inbound Links window (displayed by default for an external domain) to make sure that a direct link icon labeled with a Site #1 secondary or primary domain name is displayed there (worksheet item 14 and worksheet item 18). 5 If the link is incorrectly configured, double-click the Site #1 domain name to display the Edit Domain Link dialog box. 6 Edit the fields as necessary (worksheet item 20), then click OK to save the changes. Creating Temporary Holding Directories 58 This section applies only if the systems you are merging cannot be directly connected and you must use temporary database copies (worksheet item 4). You need to create temporary holding directories where you can place copies of the Site #2 wpdomain.db files for the primary and secondary domains (worksheet item 8). 1 For Site #2, create separate directories for the primary domain and each secondary domain. You create these directories in Site #2 to accommodate releasing the secondary domains. Each wpdomain.db file must have its own temporary directory (worksheet item 21). Name the temporary directory so that you can keep track of which domain the database belongs to. One GroupWise 6.5 Multi-System Administration Guide 2 suggested strategy is to create a temporary directory and then create subdirectories in it that match the names of'the primary and secondary domains. Make a copy of each wpdomain.db file in its appropriate holding directory. Releasing Site #2 Secondary Domains 1 2 10 11 12 13 14 In ConsoleOne, make sure you are connected to Site #2’s primary domain (worksheet item 5). In the Group Wise View, right-click the secondary domain you want to release (worksheet item 8), click GroupWise Utilities > System Maintenance to display the GroupWise System Maintenance dialog box. Select Release Secondary, then click Run to launch the Release Domain Advisor. In the Release Domain dialog box, click Next. If the Rights Warning dialog box is displayed, make sure you have sufficient rights (see “Setting Up Administrator Rights” on page 53), then click Next. Take care of any pending operations, then click Next. In the Path to Domain dialog box, select the domain directory (if it is not already displayed), then click Next. In the System Name dialog box, enter a name for the new GroupWise system that will be created for the released domain, then click Next. In the Update eDirectory Objects dialog box, select Yes if you have access to the eDirectory tree in which the domain is located, then click Next. or If you don’t have access to the domain’s eDirectory tree, select No, then click Next. After you release the domain, you will need to send the released domain’s database to someone who has access to the domain’s eDirectory tree. He or she can then use the Graft GroupWise Objects utility to update the domain’s objects in the eDirectory tree (see “Graft GroupWise Objects” in “GroupWise Utilities” in “System” in the GroupWise 6.5 Administration Guide). If you have not already done so, shut down the primary domain’s MTA and the MTA that services the domain you are releasing, then click Next. In the Ready to Release dialog box, click Release to start the release process. When the process is finished, the Domain Successfully Released dialog box is displayed. Click Done to return to the GroupWise System Maintenance dialog box, then click Close. The secondary domain has now been released to become its own GroupWise system. It is displayed as an external domain in Site #2. Restart the MTAs in case you will need to take care of any pending operations for the next domain you release. Repeat Step 2 through Step 13 for every Site #2 secondary domain you want to release (worksheet item 5 and worksheet item 10). When you have released all of the Site #2 secondary domains, you are ready to proceed with merging the domains into Site #1. For more information, see “Merging a Site #2 Domain into Site #1” on page 60. Merging the GroupWise Systems 59 However, if the systems you are merging cannot be directly connected, you must first do the tasks under “Sending Site #2 Databases to the Site #1 Administrator” on page 60 and “Receiving Site #2 Databases at Site #1” on page 60. Sending Site #2 Databases to the Site #1 Administrator This section applies only if the systems you are merging cannot be directly connected and you must use temporary database copies (worksheet item 4). Because your systems cannot be directly connected, you must send the Site #2 databases (including released secondary domains) to Site #1. 1 Create temporary holding directories on portable media, such as a disk, removable drive, or tape, to match the names of the temporary holding directories you created in Site #2 (worksheet item 21). 2 Ifyou are not the administrator for Site #1, make a record of the directory name for each database, indicating whether that database is a primary or secondary domain (worksheet item 6). 3 When you have finished copying all of the databases and recorded their details, send the portable media to the Site #1 administrator. Receiving Site #2 Databases at Site #1 This section applies only if the systems you are merging cannot be directly connected and you must use temporary database copies (worksheet item 4). 1 If you created temporary holding directories to accommodate the Site #2 system databases, copy the files from the media to your server (worksheet item 21). You will use these directories as the location for the merge of the Site #2 domains to Site #1. 2 Keep the portable media from Site #2 as an archival copy. 3 When you have copied all of the databases to temporary directories, proceed with merging the domains into Site #1. For more information, see “Merging a Site #2 Domain into Site #1” on page 60. Merging a Site #2 Domain into Site #1 1 In ConsoleOne, make sure you are connected to Site #1. 2 In the GroupWise View, right-click the Site #2 external domain that you want to merge into Site #1, then click System Maintenance (worksheet item 5 and worksheet item 10). 3 Verify that Merge External Domain is selected, then click Run to start the Merge Domain Advisor. 4 In the Merge Domain into System dialog box, click Next. 5 Ifthe Rights Warning dialog box is displayed, make sure you have sufficient rights (see “Setting Up Administrator Rights” on page 53), then click Next. 6 In the Path to Domain dialog box, enter the path to the directory containing the domain’s database (worksheet item 21), then click Next. 60 GroupWise 6.5 Multi-System Administration Guide 7 Inthe Merge External Systems dialog box, click Yes to indicate that you want the Site #2 domain to include information about its defined external systems, then click Next. This refers to systems, not domains. These are created for external synchronization. This information will include the definition and links for Site #1. 8 In the Update eDirectory Objects dialog box, select Yes if you have access to the eDirectory tree in which the domain is located, then click Next. or If you don’t have access to the domain’s eDirectory tree, select No, then click Next. After you merge the domain, you will need to send the merged domain’s database to someone who has access to the domain’s eDirectory tree. He or she can then use the Graft GroupWise Objects utility to update the domain’s objects in the eDirectory tree (see “Graft GroupWise Objects” in “GroupWise Utilities” in “System” in the GroupWise 6.5 Administration Guide). 9 If you have not already done so, shut down the primary domain’s MTA and the MTA that services the domain you are merging, then click Next. 10 In the Ready to Merge Domain dialog box, click Merge to begin the merging process. When the process has completed, the Domain Successfully Merged dialog box is displayed. 11 Click Done to exit the Merge GroupWise Domains Advisor. The merged Site #2 domain now appears as a secondary domain in Site #1. 12 Repeat Step 2 through Step 11 to merge any other external domains (that is, the secondary domains that you have released from Site #2) (worksheet item 5 and worksheet item 10). Merging the Next GroupWise System If you selected Yes for worksheet item 1, use the worksheet you completed for the next Group Wise system to be merged and begin with “Creating External Domains for Both Systems” on page 55. Sending the Merged Site #2 Databases to Site #2 This section applies only if the systems you are merging cannot be directly connected and you must use temporary database copies (worksheet item 4). The merged Site #2 domains must be sent to Site #2 so that the post office databases can be rebuilt (worksheet item 5 and worksheet item 10). 1 From Site #1, copy the merged Site #2 databases to the Site #2 domain directory. Restarting the GroupWise Agents Restart any MTAs and POAs that you shut down to complete the merge processes. Merging the GroupWise Systems 61 Testing the Merged System You should test your merged Site #1 system to make sure it is operating correctly. 1 Search the Address Book for users who were in the old Site 142 to see ifthey are now being displayed for the newly-merged Site #1. Also search the Address Book for users who were in Site #1 before the merge to see if they are still being displayed. 2 Send atest message from the primary domain to the new secondary domains (merged from Site #2) to ensure that message routing is working correctly. After you are satisfied with the operation of the merged system, you can merge the next system by starting with Chapter 8, “Planning the Merge,” on page 41. If you have already completed the planning worksheet for the next system to be merged, continue from “Creating External Domains for Both Systems” on page 55. 62 GroupWise 6.5 Multi-System Administration Guide Documentation Updates This section lists updates to the Group Wise 6.5 Multi-System Administration Guide that have been made since the initial release of GroupWise™ 6.5. The information will help you to keep current on documentation updates and, in some cases, software updates (such as a Support Pack release). The information is grouped according to the date when the GroupWise 6.5 Multi-System Administration Guide was republished. Within each dated section, the updates are listed by the names of the main table of contents sections. The GroupWise 6.5 Multi-System Administration Guide has been updated on the following dates: + “September 30, 2004” on page 63 September 30, 2004 Location Change “Planning the Merge” on Removed the top-down rebuild from the merge process. It is no longer page 41 needed. “Merge Planning Removed the top-down rebuild from the merge process. It is no longer Worksheet” on page 49 needed. “Merging the GroupWise Removed the top-down rebuild from the merge process. It is no longer Systems” on page 55 needed. Documentation Updates 63 64 GroupWise 6.5 Multi-System Administration Guide