GroupWise and DPX

The information in the remainder of this chapter assumes the reader has a strong grasp of Micro Focus GroupWise, including post offices, domains, libraries, and storage areas. A list of files needed for complete backup of these components can be found in the GroupWise Administration Guide available at http://www.Micro Focus.com/documentation. The reader is also assumed to have an understanding of GroupWise startup files.

Note. The discussions in the remainder of this chapter reflect GroupWise 7.0. They may be different in some details from other versions of GroupWise.

GroupWise Structure

The following is a brief overview of GroupWise logical and physical layouts.

Each NDS tree in a network can have an associated GroupWise system. At a minimum, the GroupWise system has a primary domain and a post office. Like NDS, the logical framework of GroupWise is hierarchical, with GroupWise domains at the top level, post offices underneath, and libraries defined within the post offices. Further, storage areas can be created for libraries that store library documents in an area other than underneath the post office.

There is also a physical layout of a GroupWise system. GroupWise is flexible enough to allow each GroupWise system process to reside on a separate server. In most organizations, each post office has its own dedicated server. Thus, a system with 3 domains, 6 post offices, 6 libraries (3 with separate storage areas) can involve 18 different servers. Additional servers may be used to house various gateway processes, but that is beyond the scope of this paper. (Most gateways do not need to be restored, even in a disaster recovery scenario.)

GroupWise services can be mixed and matched as well. For instance, on a server containing one domain and two post offices, one of the post offices may not be defined in that particular domain. However, Micro Focus strongly recommends that you run only one post office agent per server. It will be rare for more than one post office to run on a given server.

The following represents a typical GroupWise service scenario:

Server

GroupWise Service(s)

GWServer1

GWDom1 and GWDom2

GWServer2

GWPO1

GWServer3

GWPO2

GWServer4

GWPO3

GWServer5

GWPO4

GWServer6

Storage areas for GWPO4 Library2

Usually, gateways appear under their own domains (logically) and on one server (physically).

For GroupWise resources, there is an NDS/system name for a resource as well as a corresponding toplevel directory. On the windows, the GroupWise resource is shown as [resource_type]directory_name: or numeric_prefix[resource_type]:, depending on the versions of GroupWise and Micro Focus.

DPX supports GroupWise through the Target Service Agents (TSAs) recommended by Micro Focus for each Micro Focus and GroupWise platform. As a general rule, the following TSAs support the functionality described.

  • TSANDS, when running, allows the treename. and Schema resources to be shown.

  • TSAFS, when running, allows the server volumes to be shown.

  • TSAFSGW, when running, allow GroupWise Domain and Post Office volumes to be shown. Note that TSAFSGW does not apply to GroupWise 2012 and later.

  • GroupWise 2014 and GroupWise 2012 SP3 have been qualified for DPX with OES 11 SP2 x64.

Last updated