Novell GROUPWISE 8 - DOMAINS Manuel utilisateur

Domains

117

novdocx (en) 22 June 2009

Domains

Chapter 8, “Creating a New Domain,” on page 119

Chapter 9, “Managing Domains,” on page 135

Chapter 10, “Managing the Links between Domains and Post Offices,” on page 145

118 GroupWise 8 Administration Guide

novdocx (en) 22 June 2009

Creating a New Domain

119

novdocx (en) 22 June 2009

Creating a New Domain

As your GroupWise®system grows, you might need to add new domains.

Section 8.1, “Understanding the Purpose of Domains,” on page 119

Section 8.2, “Planning a New Domain,” on page 120

Section 8.3, “Setting Up the New Domain,” on page 130

Section 8.4, “What’s Next,” on page 132

Section 8.5, “Domain Worksheet,” on page 133

IMPORTANT: If you are creating a new domain in a clustered GroupWise system, see the

GroupWise 8 Interoperability Guide before you create the domain:

8.1 Understanding the Purpose of Domains

The domain functions as the main administrative unit for your GroupWise system. Each GroupWise

system has one primary domain, which was created when you first installed GroupWise. All other

domains that you add are secondary domains.

The domain serves as a logical grouping of one or more post offices and is used for addressing and

routing messages. Each GroupWise user has a GroupWise address that consists of a user ID, the

user’s post office name, the GroupWise domain name, and, optionally, an Internet domain name.

The following diagram illustrates the logical organization of a GroupWise system with multiple

domains and post offices. All of the objects under the domain belong to that domain. All of the

objects under a post office belong to that post office.

Figure 8-1 Logical Organization of a GroupWise System with Multiple Domains and Post Offices

Primary

Domain Message

Transfer

Agent

Post

Office

Post

Office

Agent

GroupWise Users

Post

Office

Post

Office

Agent

GroupWise Users

Secondary

Domain Message

Transfer

Agent

Post

Office

Post

Office

Agent

GroupWise Users

Post

Office

Post

Office

Agent

GroupWise Users

GroupWise

System

120 GroupWise 8 Administration Guide

novdocx (en) 22 June 2009

Messages are moved from user to user through your GroupWise system by the GroupWise agents.

As illustrated above, each domain must have a Message Transfer Agent (MTA) running for it. The

MTA transfers messages between domains and between post offices in the same domain. Each post

office must have at least one Post Office Agent (POA) running for it. The POA delivers messages to

users’ mailboxes and performs a variety of post office and mailbox maintenance activities.

When you add a new domain to your GroupWise system, links define how messages are routed from

one domain to another. When you add the first secondary domain, the links between the primary and

secondary domains are very simple. As the number of domains grows, the links among them can

become quite complex. Links are discussed in detail in Chapter 10, “Managing the Links between

Domains and Post Offices,” on page 145.

Physically, a domain consists of a set of directories that house all the information stored in the

domain. To view the structure of a domain directory, see “Domain Directory” in GroupWise 8

Troubleshooting 3: Message Flow and Directory Structure. The domain directory does not contain

mailboxes or messages, but it does contain other vital information. For an overview, see

Section 40.3, “Information Stored in the Domain,” on page 620. Domain directories can be located

on NetWare®, Linux, and Windows servers.

8.2 Planning a New Domain

After you have your basic GroupWise system up and running, you might need to expand it by

adding one or more domains. The GroupWise architecture lets you create a simple, single domain

system, or a complex system that links dozens of domains across a campus, a city, or around the

world.

This section provides the information you need in order to decide when, where, and how to set up a

new domain. The “Domain Worksheet” on page 133 lists all the information you need. You should

print the worksheet and fill it out as you complete the tasks listed below.

Section 8.2.1, “Determining When to Add a New Domain,” on page 120

Section 8.2.2, “Deciding Who Will Administer the New Domain,” on page 121

Section 8.2.3, “Planning Post Offices in the New Domain,” on page 122

Section 8.2.4, “Determining the Context for the Domain Object,” on page 122

Section 8.2.5, “Choosing the Domain Name,” on page 124

Section 8.2.6, “Deciding Where to Create the Domain Directory,” on page 125

Section 8.2.7, “Deciding Where to Install the Agent Software,” on page 126

Section 8.2.8, “Deciding How to Link the New Domain,” on page 129

Section 8.2.9, “Selecting the Domain Language,” on page 129

Section 8.2.10, “Selecting the Domain Time Zone,” on page 129

After you have completed the tasks and filled out the “Domain Worksheet” on page 133, you are

ready to continue with Section 8.3, “Setting Up the New Domain,” on page 130.

8.2.1 Determining When to Add a New Domain

How do you know when you should add a domain? The answer to this depends on your

administration policies and on physical and logical network organization.

Creating a New Domain 121

novdocx (en) 22 June 2009

Although a single domain can contain as many post offices and users as you want to add, there are

some conditions that indicate the need for a new domain:

Administrative Convenience: To spread out the administrative workload, you can create one

or more new domains with their own administrators. Each new domain can be managed by a

different administrator as long as each administrator has sufficient rights to connect to it and

write to the domain database.

Remote Sites: If communication between servers is slow, or if you have remote sites, you can

add a new domain to minimize mail traffic between the servers. For example, if you have

locations in three separate cities, you might have an organization that represents each location.

You could then create a domain in each organization. You could administer all of the domains

from one location or you could assign a different administrator for each one.

Demand on the MTA: Each domain has its own MTA that routes messages between post

offices within its domain. If your current domain has many post offices that are placing a heavy

workload on the MTA, you might want to create another domain to handle additional post

offices.

Multiple eDirectory Trees: All of the objects that are logically subordinate to a GroupWise

domain must be in the same Novell®eDirectoryTM tree as the domain. If you have users in other

eDirectory trees that need GroupWise accounts, you must create secondary domains and post

offices in each tree.

8.2.2 Deciding Who Will Administer the New Domain

Any user who is an Admin equivalent can administer GroupWise. We recommend that whoever

creates the new domain should be an Admin equivalent so that he or she has the necessary rights to

create objects and directories. You can then assign a different user as a domain administrator and

limit rights to other objects if necessary. For more information, see Chapter 79, “GroupWise

Administrator Rights,” on page 1177.

Depending upon the size, complexity, and layout of your eDirectory tree, you might choose a

centralized administration model with one person administering both eDirectory and GroupWise, or

you might choose a distributed administration model with the administration workload shared by

two or more individuals. With a distributed administration model, each administrator obtains rights

to the GroupWise objects and directory structures over which he or she has jurisdiction. If you want

to restrict access to some network operations or to certain domains, you can limit access rights to

domains the user should not administer.

The user assigned as the administrator must be able to create or modify objects in the domain and

will receive an e-mail message whenever an agent encounters a problem. You can designate

yourself, one or more other users, or a distribution list as an administrator.

The items in the worksheet are listed in the order you will enter them when setting up your domain.

This planning section does not follow the same order as the worksheet, but all worksheet items are

covered.

WORKSHEET

Under Item 9: Domain Administrator, enter the ID of the user or distribution list that will administer this

domain.

122 GroupWise 8 Administration Guide

novdocx (en) 22 June 2009

8.2.3 Planning Post Offices in the New Domain

Before adding the new domain, you should plan the post offices that you want to belong to the

domain. You should consider the following issues when planning post offices.

Physical Organization: If your network spans several sites, you might want to create post

offices (if not domains) at each physical location. This reduces the demands on long-distance

network links.

Logical Organization: Grouping users who frequently send messages to each other is faster

and generates less network traffic than if messages travel between different post offices and

domains.

Number of Users: A typical post office can serve from 1000 to 2500 users, depending on its

configuration. Larger post offices are possible, but grouping similar users might be preferable.

Demand on the POA: Each post office has at least one POA that delivers messages to user

mailboxes and performs other post office maintenance tasks. It is possible to run multiple

POAs, located on different servers, for the same post office, or you might prefer to create

multiple post offices.

For more details, see Section 11.2, “Planning a New Post Office,” on page 164.

8.2.4 Determining the Context for the Domain Object

When deciding where to place the new Domain object in the eDirectory tree, you should consider

how you can most easily administer GroupWise and how the domain and its associated post offices

fit into the logical organization of your eDirectory tree.

Domains and their associated objects, including Post Offices, Users, Resources, and Distribution

Lists, must be located in the same eDirectory tree. If you have multiple trees, you must create a

separate domain in each tree. The domains can all belong to the same GroupWise system, even

though they are located in different trees.

You can place the domain in any Organization or Organizational Unit container in any context in an

eDirectory tree. The following sections provide some examples of how domains can be placed in the

eDirectory tree:

“GroupWise Objects Reflect Physical Locations” on page 123

“GroupWise Objects Reflect Company Organization” on page 123

“GroupWise Objects Are Grouped with Servers” on page 123

“GroupWise Objects Are Located in a Separate GroupWise Container” on page 124

WORKSHEET

Under Item 1: Tree Name, specify the name of the eDirectory tree where you plan to create the new

domain.

Under Item 2: eDirectory Container, specify the name of the eDirectory container where you plan to

create the new domain.

Creating a New Domain 123

novdocx (en) 22 June 2009

GroupWise Objects Reflect Physical Locations

The GroupWise system below focuses on the physical layout of the company. Because most mail

traffic is probably generated by users in the same location, the mail traffic across the WAN is

minimized. An organizational unit is created for each site. A domain is created under each

organizational unit, corresponding to the city. The sites can be administered centrally or at each site.

Administrator rights can be assigned at the domain level.

Figure 8-2 A GroupWise System Following the Company’s Physical Organization

GroupWise Objects Reflect Company Organization

The following GroupWise system focuses on departmental organization, as does the eDirectory tree.

GroupWise domains and post offices parallel eDirectory organizational units, placing the domains

and post offices within the organizational units containing the users that belong to them.

Figure 8-3 A GroupWise System Following the Company’s Departmental Organization

GroupWise Objects Are Grouped with Servers

Because domains and post offices have directory structures on network servers, you could also

choose to place the Domain and Post Office objects in the same context as the servers where the

directories reside, as shown in the following example.

124 GroupWise 8 Administration Guide

novdocx (en) 22 June 2009

Figure 8-4 A GroupWise System with the Domains And Post Offices Grouped with the Servers

GroupWise Objects Are Located in a Separate GroupWise Container

Domains and post offices can also be created in their own organizational unit. Administratively, this

approach makes it easier to restrict a GroupWise administrator’s object and property rights to

GroupWise objects only. For information about GroupWise Administrator rights, see Section 8.2.2,

“Deciding Who Will Administer the New Domain,” on page 121.

Figure 8-5 Groupwise Objects Located in Their Own Organizational Unit

8.2.5 Choosing the Domain Name

The domain requires a unique name. The name is used as the Domain object’s name in eDirectory. It

is also used for addressing and routing purposes within GroupWise, and might appear in the

GroupWise Address Book.

The domain name can reflect a location, company name or branch name, or some other element that

makes sense for your organization. For example, you might want the domain name to be the location

(for example, Provo) while the post office name is one of the company’s departments (for example,

Research). Name the new domain carefully. After it is created, the name cannot be changed.

The domain name should consist of a single string. Use underscores (_) rather than spaces as

separators between words to facilitate addressing across the Internet. Do not use any of the

following invalid characters in the domain name:

ASCII characters 0-31 Comma ,

Asterisk * Double quote “

Creating a New Domain 125

novdocx (en) 22 June 2009

8.2.6 Deciding Where to Create the Domain Directory

Logically, the Domain object resides in eDirectory and is administered through ConsoleOne®.

Physically, the domain has a directory structure for databases, message queues, and other files. The

domain directory structure can be created on any of the supported platforms listed in “GroupWise

Administration Requirements” in the GroupWise 8 Installation Guide. The server where you create

the domain directory structure can be in the same tree as the Domain object or in another tree.

Many different configurations are possible. When deciding where to create the domain directory,

you should consider the following.

Domain Directory Space Requirements: The domain directory requires less than 10 MB of

free disk space. However, this requirement could increase as your system grows.

Network Access by the MTA: If the MTA is not installed on the same server with the domain

directory, the MTA must have direct network access to the domain directory so that it can write

to the domain database (wpdomain.db) and, depending on link configuration, to the post office

directories so that it can write to the POA input queues. This issue is discussed in detail in

Section 8.2.7, “Deciding Where to Install the Agent Software,” on page 126.

Security from User Access: Users never need access to the domain directory so you should

create it in a location you can easily secure; otherwise, you could have files inadvertently

moved or deleted.

Choose an empty directory for the new domain. If you want, the directory can reflect the name of the

domain, for example, res_dev for the Research and Development domain. Use the following

platform-specific conventions:

Choose the name and path carefully. After the domain directory is created, it is difficult to rename it.

If the directory you specify does not exist, it is created when you create the domain. Do not create

the domain directory under another domain or post office directory.

At sign @ Extended ASCII characters that are graphical or typographical symbols;

accented characters in the extended range can be used

Backslash \ Parentheses ( )

Braces { } Period .

Colon :

WORKSHEET

Under Item 3: Domain Name, specify the domain name.

Under Item 8: Domain Description, provide a description for the new domain.

NetWare: Use a maximum of 8 characters

Linux: Use only lowercase characters

Windows: No limitations.

126 GroupWise 8 Administration Guide

novdocx (en) 22 June 2009

8.2.7 Deciding Where to Install the Agent Software

You must run a new instance of the MTA for each new domain. To review the functions of the MTA

for the domain, see Section 40.4, “Role of the Message Transfer Agent,” on page 622. For complete

installation instructions and system requirements, see “Installing GroupWise Agents” in the

GroupWise 8 Installation Guide.

When planning the installation of the MTA, you need to consider how the new domain links to

existing domains and how the new domain will link to its post offices. For an overview of link

configuration, see Chapter 10, “Managing the Links between Domains and Post Offices,” on

page 145.

The MTA requires direct network access to the domain directory so that it can write to the domain

database (

wpdomain.db

) and, depending on the link configuration, to each post office directory so

that it can write to the POA input queues. Consider the following alternatives when selecting a

location for the MTA relative to the domain and its post offices:

“MTA Access to the New Domain: Local vs. Remote” on page 126

“MTA Access to New Post Offices: Mapped and UNC Links vs. TCP/IP Links” on page 127

“Cross-Platform Access Issues” on page 128

MTA Access to the New Domain: Local vs. Remote

Running the MTA locally on the same server where the domain and post offices reside simplifies

network connections (no login is required), reduces network traffic, and protects database integrity.

In the following diagram, the agent software is installed on the same server where the domain and

post office reside.

Figure 8-6 Agent Software on the Same Server with the Domain and Post Office

Running the MTA on a remote server allows you to place the heaviest processing load on your

highest performing server. In the following diagram, the agent software is installed on a different

server from where the domains and post offices reside.

WORKSHEET

Under Item 4: Domain Database Location, enter the full path for the domain directory.

WORKSHEET

Under Item 10: Agent Location, indicate whether you plan to run the MTA on the same server where the

domain directory is located (recommended), or on a different server.

Under Item 11: Agent Platform, enter the platform of the server where the MTA will run (NetWare, Linux,

or Windows).

Acct-Dom

Acct-PO1

POA MTA

Dev-Dom

Dev-PO1

POA MTA

Ce manuel convient aux modèles suivants

Table des matières

Autres manuels Novell Logiciel

Novell

Novell PLATESPIN ORCHESTRATE 2.0.2 - ADMINISTRATOR REFERENCE... Manuel de service

Novell

Novell IDENTITY MANAGER 3.6.1 - ENTITLEMENTS Manuel utilisateur

Novell

Novell LINUX ENTERPRISE DESKTOP 11 Manuel utilisateur

Novell

Novell PRIVILEGED USER MANAGER EVALUATION - Manuel utilisateur

Novell

Novell LINUX ENTERPRISE DESKTOP 10 - GNOME... Manuel utilisateur

Novell

Novell LINUX ENTERPRISE SERVER 10 SP3 -... Manuel

Novell

Novell IDENTITY ASSURANCE SOLUTION 3.0.2 -... Manuel utilisateur

Novell

Novell LINUX ENTERPRISE SERVER 11 - VIRTUALIZATION Manuel utilisateur

Novell

Novell PLATESPIN ORCHESTRATE 2.0.2 - DEVELOPMENT CLIENT REFERENCE... Manuel de service

Novell

Novell CLIENT FOR LINUX 2.0 SP3 - 11-2009 Manuel utilisateur

Novell

Novell IDENTITY MANAGER 3.6.1 - UNDERSTANDING POLICIES... Manuel utilisateur

Novell

Novell LINUX ENTERPRISE DESKTOP 11 - KDE 17-03-2009 Manuel utilisateur

Novell

Novell ZENWORKS PATCH MANAGEMENT 6.4 SP2 - SERVER Manuel utilisateur

Novell

Novell OPEN ENTERPRISE SERVER 2 SP2 -... Manuel utilisateur

Novell

Novell PRIVILEGED USER MANAGER 2.2.1 - ADMINISTRATION GUIDE... Manuel utilisateur

Novell

Novell ACCESS MANAGER 3.1 SP2 - README 2010 Manuel utilisateur

Novell

Novell ZENWORKS APPLICATION VIRTUALIZATION 8.0 -... Manuel utilisateur

Novell

Novell CUSTOMER CENTER 2.3 - GUIDE 4-8-2009 Manuel utilisateur

Novell

Novell IDENTITY MANAGER 3.6.1 - CLIENT LOGIN EXTENSION... Manuel utilisateur

Novell

Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - COMMAND LINE UTILITIES REFERENCE 10.3... Manuel technique

Novell

Novell BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 -... Manuel utilisateur

Novell

Novell LINUX ENTERPRISE DESKTOP 11 Mode d’emploi

Novell

Novell DATA SYNCHRONIZER - 07-2010 Manuel utilisateur

Novell

Novell EDIRECTORY 8.8 SP5 - GUIDE 12-2009 Manuel utilisateur

Manuels Logiciel populaires d'autres marques

COMPRO

COMPRO COMPROFM Manuel utilisateur

Muratec

Muratec OFFICEBRIDGE ONLINE Manuel utilisateur

Oracle

Oracle Contact Center Anywhere 8.1 Manuel utilisateur

Adobe

Adobe 65007312 - Photoshop Lightroom Manuel

Avaya

Avaya NULL One-X for RIM Blackberry Manuel utilisateur

HP ProLiant BL420c Manuel utilisateur

PS Audio

PS Audio PowerPlay Manuel du propriétaire

Brady

Brady LOCKOUT PRO 3.0 Manuel de service

Avaya

Avaya Interaction Center Manuel utilisateur

Texas Instruments

Texas Instruments TI-83 Plus Silver Edition Manuel

Oracle

Oracle Application 9i Manuel utilisateur

Acer

Acer RDM Manuel utilisateur

Canon

Canon Vixia HF21 Manuel utilisateur

Canon

Canon ZR950 Manuel utilisateur

Samsung

Samsung Auto Backup Manuel utilisateur

Polycom

Polycom Vortex EF2201 Instructions d'installation et d'utilisation

Brocade Communications Systems

Brocade Communications Systems Brocade 8/12c Manuel utilisateur

Lexmark

Lexmark Apps Manuel de service