Creating the GroupWise Primary Domain

The primary domain is the first thing that actually denotes the physical creation of a GroupWise system. The primary domain serves as the following:

• The "master" of the GroupWise system

• An object in eDirectory

• A set of files and directories/folders needed for any GroupWise domain, physically located at a specific UNC path on a file server

Because the primary domain must serve all of these functions, it is important that you carefully plan for it.

Choosing Your Primary Domain Name

Choose domain names carefully, because you cannot change them after you've created them. Figure 2.5 shows the prompt for the primary domain name. We suggest using naming conventions that adhere closely to those used in your eDirectory tree and server environment. WorldWide Widgets will call its primary domain CORP. Don't use any of the following invalid characters when naming the domain:

• ASCII characters 013

• The "at" sign @

• Braces {}

• Parentheses ()

• A colon :

• A comma ,

• A period .

• A space

• A double quote "

Figure 2.5. Naming a primary domain

Tip

If possible, keep domain and post office names equal to or shorter than eight characters in length. This makes it easy to have directory names that match the name of the domain and helps avoid confusion. Also, with the (possible) introduction of Linux, avoid using uppercase in any of your directory names.

Selecting a Primary Domain Directory

This is where the primary domain will physically reside. This directory must be on a file server. It need not be on a NetWare server, though; it can also be on a Linux or Windows server. Specify a path that is no longer than eight characters in length. The path should not contain spaces or periods and should be made up of only letters, numbers, and dashes or underscores. For domains on the Linux platform, make certain that the name for the directory is indicated in lowercase. Do not create a domain directory in uppercase, because the Linux GroupWise Message Transfer Agent does not like uppercase directory names.

Warning

Never give your users file access to a domain directory. They don't need it, and if they arbitrarily delete files, you might be in a world of hurt.

Specifying the Domain Context

This is where you place the GroupWise primary domain object in your eDirectory tree. The domain context is important only from an administration standpoint. If your company implements security controls on eDirectory objects, for example, you might want to have a container for GroupWise objects. You might want to use organizational role objects to administer trustee assignments to the GroupWise system. In this way, you can control which of the system administrators can perform GroupWise administration operations.

WorldWide Widgets has decided to make its GroupWise domain structure match its eDirectory Organization Unit structure. In large systems, in which operators all over the network are making changes in eDirectory, creating a GroupWise OU helps non-GroupWise administration personnel understand the separate purpose of the GroupWise objects. As shown in Figure 2.6, you will be prompted for the eDirectory OU to place the primary domain object into.

Figure 2.6. Primary domain eDirectory context

Note

If you need to move a GroupWise domain or post office to a new eDirectory container, refer to Chapter 21, "Moving Domains and Post Offices."

Letting GroupWise Know Your Time Zone

By specifying which time zone a GroupWise post office or domain is in, you affect how appointment and status message timestamps are created. Be sure to specify the correct time zone information or people will miss appointments. The time zone for the primary domain will be the time zone for the location where the file server is that will house the GroupWise primary domain. Be aware that for many reasons a GroupWise environment maintains its own daylight saving time (DST) scheme, independent of the underlying server which might change to DST on other dates. Chapter 6 covers time zone administration in more detail.

Giving the Post Office a Name

Although you might not want to create a post office yet, the installation wizard requires you to do so. The name of a post office cannot be changed, so choose wisely!

It is also possible that you have no intention to keep the post office that the wizard requires you to create. If that is the case, no particular care needs to be taken in creating the post office. After the wizard is complete, you will just delete the post office.

Giving the Post Office a Home: The Post Office Directory

The post office directory is the physical location for the GroupWise post office. A GroupWise post office is a set of files and a directory structure. All GroupWise post offices have the same kind of structure. Specify a path that is no longer than eight characters in length. The path should not contain spaces or periods but should be made up only of letters, numbers, and dashes or underscores. For post offices on the Linux platform, make certain that the name for the directory is indicated in lowercase. Do not create a post office directory in uppercase, because the Linux GroupWise Post Office Agent does not like uppercase directory names.

The post office contextis where the post office object will be placed in your eDirectory tree. This context is important to your users, for reasons explained further in Chapter 12, "Administering the GroupWise Client." The GroupWise client can use eDirectory to authenticate users to their mailboxes; having the post office in the same context as your users speeds up authentication. If you place post offices in contexts where users have no trustee assignments, you will create administration headaches for yourselflater.

Note

There is no security risk inherent in allowing users to have browse, read, and compare rights to post office objects in the eDirectory tree.

Defining a Post Office Link

Each post office communicates with the rest of the GroupWise system through the domain's MTA. For the MTA to "talk" with a post office, it needs a way to hand messages to the post office. An MTA can either drop off and pick up files at the post office via a UNC connection, or transmit files via TCP/IP to the POA servicing the post office. Figure 2.7 shows the post office link prompt. A UNC link is called a direct link in this screen. A TCP/IP link is just as direct, however, and almost always preferred. These are the choices available:

• Direct Link: This older method of linking a domain to a post office requires that the MTA have file system rights to the UNC path where the post office is. A direct link is sometimes used, particularly if your GroupWise post office is on the same file server that houses the domain that owns the post office. In most cases, even if a domain and a post office are on the same file server, it is better to configure a TCP/IP connection between the MTA and the POA. The Linux MTA does not support a direct link type; only a TCP/IP link is supported.

• TCP/IP Link: This is the preferred method for linking the domain's MTA with a post office's POA and the only method available for a Linux environment.

Figure 2.7. Post office link

Selecting Post Office Users

You can select users to be associated with this post office at this point. You also can do this later as you create additional users.

Tip

One advantage to not selecting users for the post office yet is that GroupWise enables you to set a system-wide default password. By not selecting users to add to the GroupWise system at this point, you can set up this default password feature and then add the users to the GroupWise system. You'll learn more about setting a default system password in Chapter 6.