Related Manuals for Novell GROUPWISE 7 - MULTI-SYSTEM ADMINISTRATION
Summary of Contents for Novell GROUPWISE 7 - MULTI-SYSTEM ADMINISTRATION
- Page 1 Novell GroupWise ® w w w . n o v e l l . c o m M U L T I - S Y S T E M A D M I N I S T R A T I O N...
- Page 2 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.
- Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
-
Page 5: Table Of Contents
Contents About This Guide Part I Connecting to GroupWise 5.x, 6.x, and 7.x Systems 1 Understanding Connection Options Connection Methods Supported by the Various GroupWise Versions ....13 Dynamic Internet Links . - Page 6 4 Using Gateway Links Connecting Systems Through the Internet ........33 Connecting Systems Through an Asynchronous Phone Line .
- Page 7 11.6 Sending Site #2 Databases to the Site #1 Administrator ......72 11.7 Receiving Site #2 Databases at Site #1 .
- Page 8 GroupWise 7 Multi-System Administration Guide...
-
Page 9: About This Guide
Troubleshooting Guides GroupWise Client User Guides GroupWise Client Frequently Asked Questions (FAQ) 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 ( , etc.) denotes a Novell trademark. - Page 10 When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash. Users of platforms that require a forward slash, such as Linux*, should use forward slashes as required by your software. When a startup switch can be written with a forward slash for some platforms or a double hyphen for other platforms, the startup switch is presented with a forward slash.
-
Page 11: Part I Connecting To Groupwise 5.X, 6.X, And 7.X Systems
Connecting to GroupWise 5.x, 6.x, and 7.x Systems Chapter 1, “Understanding Connection Options,” on page 13 Chapter 2, “Using Dynamic Internet Links,” on page 17 Chapter 3, “Using Direct Links,” on page 27 Chapter 4, “Using Gateway Links,” on page 33 Chapter 5, “Synchronizing External GroupWise Systems,”... - Page 12 GroupWise 7 Multi-System Administration Guide...
-
Page 13: Understanding Connection Options
Understanding Connection Options ® When connecting your GroupWise 7.x system with another GroupWise 5.x, 6.x, or 7.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: Section 1.1, “Connection Methods Supported by the Various GroupWise Versions,”... -
Page 14: Dynamic Internet Links
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 GroupWise Message Transfer Protocol (GWMTP) to connect with and transfer messages to the destination MTA. - Page 15 Understanding Connection Options...
- Page 16 GroupWise 7 Multi-System Administration Guide...
-
Page 17: Using Dynamic Internet Links
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. -
Page 18: Setting Up Internet-Style Addressing
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 GroupWise systems to route messages that contain your Internet domain names to the appropriate MTAs in your system. -
Page 19: Creating The Service ("Srv") Or Text ("Txt") Record
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. -
Page 20: Configuring The Mta's Server For Dns Lookups
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 172.16.5.18 Consult your NetWare documentation for more detailed information about configuring a NetWare server for DNS lookups. -
Page 21: Enabling Mtas To Perform Dns Lookups
2.6 Enabling MTAs to Perform DNS Lookups After you have performed the necessary configuration to enable an MTA’s server to allow DNS lookups (see Section 2.5, “Configuring the MTA’s Server for DNS Lookups,” on page 20), you must configure the MTA to perform DNS lookups. By default, your GroupWise system is configured not to allow MTAs to perform DNS lookups. -
Page 22: Enabling/Disabling Dns Lookups For Individual Mtas
2.6.2 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 21), you can disable DNS lookups for individual MTAs. -
Page 23: Understanding Dynamic Internet Links
2.7 Understanding Dynamic Internet Links The following diagram illustrates the basic process of establishing a dynamic Internet link between GroupWise systems. ctp.com GWMTP GWIA Domain Undeliverable Look up Undeliverable SMTP Domain Undeliverable Mail Server 2.7.1 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. -
Page 24: Stage 3: Groupwise Mta In The Sending System
If No: The client recognizes the Internet domain as external to its system and queues the message to the MTA. Go to Stage 2.7.3 Stage 3: GroupWise MTA in the Sending System The GroupWise MTA asks: “Does the Internet domain in this address match any Internet domain defined in the local GroupWise system?”... -
Page 25: Stage 8: Groupwise Internet Agent In The Sending System
2.7.8 Stage 8: GroupWise Internet Agent in the Sending System The designated Internet Agent establishes an SMTP link with the Internet domain in the address, converts the GroupWise message to SMTP format, and sends the message to the other messaging system through the SMTP Internet connection. - Page 26 GroupWise 7 Multi-System Administration Guide...
-
Page 27: Using Direct Links
Using Direct Links ® When you connect two domains in different GroupWise 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 GroupWise users. -
Page 28: Creating An External Domain
System Synchronization” in “GroupWise System Operations” in “System” in the GroupWise 7 Administration Guide. 3.2 Creating an External Domain The first step in connecting two GroupWise systems via a direct link is to create an external domain in each GroupWise system. The external domain represents a domain in the other GroupWise system and provides the medium through which you define the link to the other system. -
Page 29: Linking To The External Domain
4 Repeat Step 1 through Step 3 to define an external domain in the second GroupWise system. If you do not have administrative rights to that system, you need to coordinate with that GroupWise system’s administrator. 5 Continue with the next section, Linking to the External Domain. -
Page 30: Checking The Link Status Of The External Domain
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 7 Administration Guide. -
Page 31: Exchanging Information Between Systems
recipients from the other system. For information, continue with Exchanging Information Between Systems. 3.6 Exchanging Information Between Systems Exchanging information between two GroupWise 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... - Page 32 GroupWise 7 Multi-System Administration Guide...
-
Page 33: Using Gateway Links
GroupWise 4.1 gateways work with GroupWise 4.1, 5.x, 6.x., and 7.x. GroupWise 5.x gateways work with GroupWise 5.x, 6.x, and 7.x. For the most current GroupWise gateway product ® information, contact your local Novell office (http://www.novell.com/index/wwoffices.html). 4.1 Connecting Systems Through the Internet The Internet now links thousands of networks and workstations throughout the world. -
Page 34: Connecting Systems Through An Asynchronous Phone Line
The GroupWise Async Gateway provides this capability. For more information, see the GroupWise Async Gateway Guide at the GroupWise Gateways Documentation Web site (http://www.novell.com/ documentation/gwgateways). 4.3 Connecting Systems Through an X.25 Line X.25 lines can also be used to connect GroupWise systems on different networks. - Page 35 For information about these gateways, see the GroupWise Gateway Documentation Web site (http:/ /www.novell.com/documentation/gwgateways). Using Gateway Links...
- Page 36 GroupWise 7 Multi-System Administration Guide...
-
Page 37: Synchronizing External Groupwise Systems
Synchronizing External GroupWise Systems The External System Synchronization feature lets you automatically synchronize information ® between your system and an external GroupWise system connected to your system (for information about connecting GroupWise systems, see “Connecting to GroupWise 5.x, 6.x, and 7.x Systems”... - Page 38 2 Click Add to display the Add External GroupWise System dialog box. 3 Fill in the following fields: External System Name: Specify the name of the external GroupWise system. The name needs to match the actual name of that GroupWise system. Description: If desired, enter a description for the external system.
- Page 39 4 Click OK to add the external GroupWise system to the list of external systems you are synchronizing information with. 5 Click Close to save your changes. After External System Synchronization is configured in both GroupWise systems, the two systems exchange information.
- Page 40 GroupWise 7 Multi-System Administration Guide...
-
Page 41: Part Ii Connecting To Non-Groupwise Messaging Systems
Connecting to Non-GroupWise Messaging Systems Chapter 6, “GroupWise Internet Agent,” on page 43 Chapter 7, “GroupWise Gateways,” on page 45 Connecting to Non-GroupWise Messaging Systems... - Page 42 GroupWise 7 Multi-System Administration Guide...
-
Page 43: Groupwise Internet Agent
GroupWise Internet Agent The preferred way to connect to non-GroupWise messaging systems is through the Internet. ® GroupWise provides connectivity to the Internet through the GroupWise 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. - Page 44 GroupWise 7 Multi-System Administration Guide...
-
Page 45: Groupwise Gateways
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). For GroupWise gateway documentation, see the GroupWise Gateway Documentation Web site (http://www.novell.com/documentation/gwgateways). GroupWise Gateways... - Page 46 GroupWise 7 Multi-System Administration Guide...
-
Page 47: Part Iii Merging With Groupwise 5.X, 6.X, And 7.X Systems
Merging with GroupWise 5.x, 6.x, I I I and 7.x Systems Chapter 8, “Why Merge GroupWise Systems?,” on page 49 Chapter 9, “Planning the Merge,” on page 51 Chapter 10, “Preparing for the Merge,” on page 65 Chapter 11, “Merging the GroupWise Systems,” on page 67 Merging with GroupWise 5.x, 6.x, and 7.x Systems... - Page 48 GroupWise 7 Multi-System Administration Guide...
-
Page 49: Why Merge Groupwise Systems
Why Merge GroupWise Systems? If you are consolidating organizations or combining departments, you might want to merge two or ® more GroupWise 5.x 6.x, or 7.x systems rather than connect them (see “Connecting to GroupWise 5.x, 6.x, and 7.x Systems” on page 11). - Page 50 GroupWise 7 Multi-System Administration Guide...
-
Page 51: Planning The Merge
Planning the Merge Section 9.7, “Merge Planning Worksheet,” on page 59 lists all the information you need as you ® merge a GroupWise 5.x, 6.x, or 7.x system into your GroupWise 7.x system. Section 9.1, “Understanding the Merge Process,” on page 51 Section 9.2, “Planning Administrator Rights,”... - Page 52 The following GroupWise agent functions are not 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.
-
Page 53: Planning Administrator Rights
WORKSHEET Under Item 16: Site #1 Name, enter the name of the GroupWise system to designate as Site #1. Under Item 7: Site #2 Name, enter the name of the GroupWise system to designate as Site #2. If you are merging three or more GroupWise systems, you will select a different system as Site #2 each time you reuse this planning section and rerun the merge process. -
Page 54: Planning The Location Of The Domain Database Backup Directories
9.4 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 arise during the merge process. -
Page 55: 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... -
Page 56: Linking The Domains
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. -
Page 57: Releasing The Secondary Domains In Site #2
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. -
Page 58: Planning To Merge Additional Groupwise Systems
9.6 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. -
Page 59: Merging At Different Times
WORKSHEET Do the following on each additional worksheet: Under Item 16: Site #1 Name, enter the name of the GroupWise system to designate as Site #1. Under Item 7: Site #2 Name, enter the name of the GroupWise system to designate as Site #2. If you are merging three or more GroupWise systems, you will select a different system as Site #2 each time you reuse this planning section and rerun the merge process. - Page 60 Item Example Explanation 3) GroupWise Objects to None List any eDirectory user objects, Delete: 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 Section 9.3, “Determining Which GroupWise Objects Are No Longer In Use,”...
- Page 61 Item Example Explanation 8) Site #2 External Headquarters There must be at least one direct link Domain Names: 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.
- Page 62 Item Example Explanation 13) Site #1 External Branch1 You must have an external domain in Site Domain Names: #1 for each primary and secondary domain Distribution 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.
- Page 63 Item Example Explanation 19) Descriptions for Site Branch1 - primary Enter an informative description for each #1 External Domains: Site #1 external domain. Distribution - secondary For more information, see “External Domains” on page 20) Link Configuration Headquarters Fill in the fields once for each link being set Fields: Direct For more information, see...
- Page 64 Item Example Explanation 24) Paths to Site #1 To protect against losing information in \\gw\sys\bak\research Backup Directories: case of error, you need a backup of each \\gw\sys\bak\headq Site #1 domain database. You should place each wpdomain.db file in a separate \\gw\sys\bak\account backup directory.
-
Page 65: Preparing For The Merge
Section 10.4, “Resolving Pending Operations,” on page 66 10.1 Setting Up Administrator Rights ® Make sure the administrator performing the move is an admin-equivalent in Novell eDirectory (worksheet item Make sure the administrator also has access to the GroupWise systems being merged. -
Page 66: Resolving Pending Operations
10.4 Resolving Pending Operations When you release secondary domains in Site #2, you are 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 GroupWise system for Site #2, then click Tools >... -
Page 67: Merging The Groupwise Systems
Merging the GroupWise Systems The information in this section helps you to merge Site #2 into Site #1. The Merge Planning Worksheet contains all the information the merge process prompts 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 section.) Some tasks apply only to systems that cannot be directly connected. -
Page 68: Creating Site #1 External Domains In Site #2
11.1.1 Creating Site #1 External Domains in Site #2 ® 1 In ConsoleOne , make sure you are connected to the Site #2 GroupWise system (worksheet item 2 Right-click GroupWise System in the GroupWise View, then click New > External Domain to display the Create External GroupWise Domain dialog box. -
Page 69: Configuring Links Between Site #2 Domains And Site #1 Secondary Domains
2 Right-click GroupWise System in the GroupWise View, then click New > External Domain to display the Create External GroupWise Domain dialog box. 3 Fill in the fields: Domain Name: Enter the name of the Site #2 domain you are connecting to (worksheet item 5 worksheet item 10). -
Page 70: Checking Links To Site #1 External Domains In Site #2
“Checking Links to Site #2 External Domains in Site #1” on page 70 11.3.1 Checking Links to Site #1 External Domains in Site #2 You 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. -
Page 71: Releasing Site #2 Secondary Domains
temporary directory so that you can keep track of which domain the database belongs to. One suggested strategy is to create a temporary directory and then create subdirectories in it that match the names of the primary and secondary domains. 2 Make a copy of each wpdomain.db file in its appropriate holding directory. -
Page 72: Sending Site #2 Databases To The Site #1 Administrator
However, if the systems you are merging cannot be directly connected, you must first do the tasks under Section 11.6, “Sending Site #2 Databases to the Site #1 Administrator,” on page 72 Section 11.7, “Receiving Site #2 Databases at Site #1,” on page 11.6 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... -
Page 73: Merging The Next Groupwise System
7 In the 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 includes the definition and links for Site #1. -
Page 74: Testing The Merged System
11.12 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 #2 to see if they are now being displayed for the newly-merged Site #1. -
Page 75: A Documentation Updates
Noted that you need to include the gwdom.cd file along with each domain Temporary Holding database. Directories,” on page 70 A.2 June 15, 2006 Location Change ® Entire Guide Page design reformatted to comply with revised Novell documentation standards. Documentation Updates...