1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. GROUPWISE 8 - INTEROPERABILITY
  6. Manual

Novell GROUPWISE 8 - INTEROPERABILITY Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
AUTHORIZED DOCUMENTATION
Interoperability Guide
Novell
®
GroupWise
®
8
August 31, 2009
www.novell.com
GroupWise 8 Interoperability Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the GROUPWISE 8 - INTEROPERABILITY and is the answer not in the manual?

Questions and answers

Related Manuals for Novell GROUPWISE 8 - INTEROPERABILITY

Summary of Contents for Novell GROUPWISE 8 - INTEROPERABILITY

  • Page 1 AUTHORIZED DOCUMENTATION Interoperability Guide Novell ® GroupWise ® August 31, 2009 www.novell.com GroupWise 8 Interoperability Guide...
  • 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 4 GroupWise 8 Interoperability Guide...

  • Page 5: Table Of Contents

    Updating GroupWise Objects with Cluster-Specific Descriptions ....57 3.7.2 Using Novell Remote Manager on NetWare 6.5 ......58 3.7.3 Knowing What to Expect in MTA and POA Failover Situations .
  • Page 6 3.9.2 Domain Quick Checklist..........63 3.9.3 Post Office Quick Checklist .
  • Page 7 Installing Novell Cluster Services on Linux ........
  • Page 8 14.5 Testing Your Clustered GroupWise System........154 14.6 Managing Your Clustered GroupWise System.
  • Page 9 23 Using GroupWise with Novell Teaming 23.1 Understanding How Novell Teaming Interacts with eDirectory and GroupWise ..239 23.2 Using eDirectory as the Teaming LDAP Directory ....... . . 239 23.3...
  • Page 10 Preparing for GroupWise Integration with Conferencing ..... 243 24.1.2 Integrating GroupWise with Novell Conferencing ......243 24.1.3 Testing GroupWise as the Novell Conferencing E-Mail System .
  • Page 11 30 GroupWise Customization Tools 31 Novell exteNd Part VI Microsoft Clustering Services on Windows 32 Introduction to GroupWise 8 and Microsoft Clusters 33 Planning GroupWise in a Microsoft Cluster 33.1 Setting Up Your Microsoft Cluster ..........278 33.2...
  • Page 12 35.1.5 Deciding Where to Install the Internet Agent and Its MTA ....307 35.1.6 Planning the MTA Installation ......... 308 35.1.7 Planning the Internet Agent Installation .
  • Page 13 41.2.1 Installing the Messenger Agents to Each Node in the Cluster....338 41.2.2 Installing the Messenger Agents to a Shared Disk ......338 41.3 Messenger Clustering Worksheet .
  • Page 14 GroupWise 8 Interoperability Guide...

  • Page 15: About This Guide

    GroupWise 8 Troubleshooting 3: Message Flow and Directory Structure Novell Support and Knowledgebase (http://www.novell.com/support) To search the GroupWise documentation from the Novell Support Web site, click Advanced Search, select Documentation in the Search In drop-down list, select GroupWise in the Products drop-down list, type the search string, then click Search.
  • Page 16 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 within a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark.

  • Page 17: Part I Novell Cluster Services On Netware

    Novell Cluster Services on NetWare Chapter 1, “Introduction to GroupWise 8 and Novell Cluster Services on NetWare,” on page 19 Chapter 2, “Planning GroupWise in a NetWare Cluster,” on page 21 Chapter 3, “Setting Up a Domain and Post Office in a NetWare Cluster,” on page 41 Chapter 4, “Implementing the Internet Agent in a NetWare Cluster,”...
  • Page 18 GroupWise 8 Interoperability Guide...

  • Page 19: Introduction To Groupwise 8 And Novell Cluster Services On Netware

    Before implementing GroupWise 8 with Novell Cluster Services , make sure you have a solid understanding of Novell Cluster Services by reviewing the following information resources: AppNote: An Introduction to Novell Cluster Services (http://developer.novell.com/research/ appnotes/1999/may/01/a990501_.pdf) Novell Open Enterprise Server (OES) Product Documentation: OES Novell Cluster Services 1.8 Administration Guide for NetWare (http://www.novell.com/documentation/oes/...
  • Page 20 A shared volume for which a Volume Resource object has been created in Novell eDirectory . The properties of the Volume Resource object provide load and unload scripts for programs installed on the volume, failover/failback/migration policies for the volume, and the failover path for the volume.

  • Page 21: Planning Groupwise In A Netware Cluster

    107) is designed for those who are creating a new ® ® GroupWise system, or at least new domains and post offices, in the context of Novell Cluster Services . If you already have an existing GroupWise 8 system and need to configure it to work in a newly installed cluster, see Chapter 10, “Moving an Existing GroupWise 8 System into a NetWare...

  • Page 22: Meeting Software Version Requirements

    Installing the Novell Cluster Services software on all nodes in the cluster Mounting the shared volumes where you will set up GroupWise domains and post offices and install the GroupWise agents As you install Novell Cluster Services, record key information about the cluster on the System Clustering Worksheet: SYSTEM CLUSTERING WORKSHEET...

  • Page 23: Planning A New Clustered Domain

    Parts of your GroupWise system can run in one cluster while other parts of it run in one or more other clusters. Parts of your GroupWise system can run in a cluster while other parts run outside of the cluster, on non-clustered servers.

  • Page 24: Planning A New Clustered Post Office

    Regardless of the type of domain you are creating, keep in mind the following cluster-specific details as you fill out the worksheet you need: When you specify the location for the domain directory (and for a new GroupWise system, the post office directory) on the worksheet, include the shared volume where you want the directory to reside.

  • Page 25: Planning A New Library For A Clustered Post Office

    NetWare, as listed in Chapter 1, “Introduction to GroupWise 8 and Novell Cluster Services on NetWare,” on page The advantages of cluster-enabling GroupWise volumes include: Drive mappings always occur through the virtual server associated with the cluster-enabled volume, rather than through a physical server.
  • Page 26 eDirectory Objects Used in a Cluster Table 2-1 eDirectory Object Name and Description Object clustername_volumename (default object name) A new Volume object represents the cluster-enabled volume. It is created by renaming the original Volume object that was tied to a physical server and associating it with a virtual server instead.

  • Page 27: Ensuring Successful Name Resolution For Groupwise Volumes

    If you decide not to cluster-enable GroupWise volumes, you should adjust the steps presented in this documentation for your system’s specialized needs. Novell Cluster Services does provide a GroupWise Mail Server template for use when creating GroupWise Cluster Resource objects instead of cluster-enabled Volume Resource objects.

  • Page 28: Deciding How To Install And Configure The Agents In A Cluster

    For short name resolution to work using DNS, the client workstation must either belong to the same DNS zone (such as provo.novell.com) as the cluster resource, or the cluster resource zone must be configured in the client’s DNS suffix search path under TCP/IP settings for the workstation.

  • Page 29: Planning Secondary Ip Addresses And Cluster

    Section 2.8.4, “Deciding Whether to Run the Agents in Protected Memory,” on page 34 Section 2.8.5, “Planning the NetWare Agent Installation,” on page 34 2.8.1 Planning Secondary IP Addresses and Cluster-Unique Port Numbers for Agents in the Cluster The GroupWise agents listen on all IP addresses, both primary and secondary, that are bound to the server on their specified port numbers.
  • Page 30 WebAccess Information WebAccess WebAccess WebAccess WebAccess Agent IP Address MTP Port HTTP Port Agent Port HTTP Port WebAccess 172.16.5.84 7120 7184 Domain MTA WebAccess Agent (same as MTA) 7205 7205 (GWINTER) (same as agent) This example places the Development post office on the same node and on the same GroupWise volume with the Provo1 domain;...

  • Page 31: Determining Appropriate Failover Paths For The Agents

    SYSTEM CLUSTERING WORKSHEET If you are setting up a new GroupWise system, under Item 6: Shared Volumes for GroupWise Administration, specify secondary IP addresses for your GroupWise administration volumes. Under Item 7: Shared Volume for Domain, use the domain MTA secondary IP address from the IP Address Worksheet as the domain volume IP address.
  • Page 32 Agent Software Installation Locations Table 2-3 Location Description sys:\system This is the default location provided by the Agent Installation program. Because on each node the agents must be installed on each node where they might need to run during in the cluster a failover situation, you need to do one of the following if you select this alternative: Run the Agent Installation program multiple times in order to install the...
  • Page 33 If you ever need to add or replace a physical server in the cluster, you only need to install NetWare and Novell Cluster Services to the new server, then add that node to the appropriate failover paths. No extra GroupWise configuration is necessary because there are no dependencies for the GroupWise agents.

  • Page 34: Deciding Whether To Run The Agents In Protected Memory

    2.8.4 Deciding Whether to Run the Agents in Protected Memory On a NetWare server, using protected memory allows you to create isolated memory spaces where programs can run without affecting other NLM programs running on the same node. This contributes to the high availability of the cluster. Using protected memory has the following advantages: When using protected memory, the node can restart a specific memory space if any NLM program within that memory space abends.

  • Page 35: Groupwise Clustering Worksheets

    For more information, see Section 2.1, “Meeting Software Version Requirements,” on page 2) eDirectory Tree for Cluster: Record the eDirectory tree where you created the new Novell Cluster object when you installed Novell Cluster Services. For more information, see Section 2.2, “Installing Novell Cluster Services,”...
  • Page 36 For more information, see Section 2.2, “Installing Novell Cluster Services,” on page 4) Cluster Context: Record the full context where you created the new NetWare Cluster object.

  • Page 37: Ip Address Worksheet

    Item Explanation 8) Shared Volume for Post Office: Specify the name (cluster_volume) of the shared volume where the GroupWise post office will reside. Cluster Enabled? For cluster-enabling, specify the IP address of the virtual Yes (highly recommended) server (volume_SERVER.cluster) to which the cluster-enabled volume is tied.
  • Page 38 Domain Information Domain IP Address MTP Port HTTP Port Post Office Information Post Office IP Address C/S Port MTP Port HTTP Port Internet Agent Information GWIA GWIA Internet Agent Live Remote IP Address MTP Port HTTP Port HTTP Port Port GWIA Domain Internet Agent (same)

  • Page 39: Agent Clustering Worksheet

    2.9.3 Agent Clustering Worksheet Item Explanation 1) agent installation location: Mark the location where you will install the agent software. on the GroupWise vol:\system If necessary, specify the location where you will volume consolidate multiple agent startup files on a GroupWise sys:\system on each node volume.
  • Page 40 GroupWise 8 Interoperability Guide...

  • Page 41: Setting Up A Domain And Post Office In A Netware Cluster

    2 Complete the steps in the cluster-enabling section of the cluster documentation for your version ® of NetWare , as listed in Chapter 1, “Introduction to GroupWise 8 and Novell Cluster Services on NetWare,” on page Setting Up a Domain and Post Office in a NetWare Cluster...

  • Page 42: Configuring Short Name Resolution

    The System Clustering Worksheet provides the volume to cluster-enable for use the GroupWise, the cluster-enabled volume IP address, and the failover path for the GroupWise volume. For a review of the new Novell eDirectory objects that are created when you cluster-enable a shared volume, see Section 2.6, “Deciding Whether to Cluster-Enable the Shared Volumes...
  • Page 43 Hosts Files Because each GroupWise volume where you plan to create a domain or post office has been associated with a virtual server, you should add lines for the new virtual servers to one or more of the following files as needed: NetWare: sys:\etc\hosts (on all nodes in the cluster;...

  • Page 44: Setting Up A New Groupwise System In A Cluster

    Use System Clustering Worksheet item 3 cluster. On NetWare 6.5, Novell Cluster Services automatically propagates virtual server information into SLP and provides the most reliable name resolution. 3.2 Setting Up a New GroupWise System in a...

  • Page 45: Creating A New Secondary Domain In A Cluster

    Do not create users in the post office at this time. In the Summary dialog box, the domain directory and post office directory that you browsed to should display as UNC paths using the virtual server name with the GroupWise volume. 5 When you have finished creating the primary domain and the initial post office, continue with installing the GroupWise Agents, starting with Step 4 on page 49...

  • Page 46: Creating A New Post Office In A Cluster

    5 Create the new domain, following the steps provided in “Creating the New Domain” in “Domains” in the GroupWise 8 Administration Guide. Keep in mind the following cluster- specific details: Use the Domain Worksheet you filled out in Section 2.3, “Planning a New Clustered Domain,”...
  • Page 47 2 Manually create the post office directory (System Clustering Worksheet item 12). This step is not required, but in a clustered environment, Step 4 is easier if the post office directory already exists. 3 In ConsoleOne, connect to the GroupWise domain where you want to create the new post office, as described in “Connecting to a Domain”...

  • Page 48: Installing And Configuring The Mta And The Poa In A Cluster

    The database rebuild is necessary in order to transfer the POA configuration information and the post office link information into the post office database, because the POA for the new post office is not yet running. 10 If you want to create a library with its document storage area outside the post office directory, (System Clustering Worksheet item 14), follow the steps in “Setting Up a Basic...

  • Page 49: Editing Clustered Agent Startup Files

    3 Start the Agent Installation program, following the steps provided in “Installing the NetWare Agent Software” in “Installing GroupWise Agents” in the GroupWise 8 Installation Guide. 4 Install the NetWare agents, keeping in mind the following cluster-specific details: Use the NetWare Agent Clustering Worksheet that you filled out in “Planning the NetWare Agent Installation”...

  • Page 50: Configuring The Groupwise Volume Resource To Load And Unload The Agents

    information is available to the POA in its eDirectory object properties. However, in some failover situations, reconnection to the MTA is improved when the information is immediately available to the POA in its startup file. If you are running the POA in protected memory and your version of NetWare requires it, add the user /password startup switches (under...
  • Page 51 If you selected on each node as the installation location (Agent Clustering sys:\system Worksheet item 1) but you are storing the agent startup files on the GroupWise volume, add that location to the server search path. If you marked No under Load Agents in Protected Memory? (Agent Clustering Worksheet item 8), add the following abend recovery options:...
  • Page 52 5 If necessary, click OK to confirm that you must offline and then online the volume resource in order for the changes to take effect. 6 Continue with Modifying the Volume Resource Unload Script for the Agents. Modifying the Volume Resource Unload Script for the Agents The volume resource unload script executes whenever the GroupWise volume goes offline.
  • Page 53 NetWare, as listed in Chapter 1, “Introduction to GroupWise 8 and Novell Cluster Services on NetWare,” on page 5 Click OK when you are finished editing the GroupWise volume resource properties.

  • Page 54: Setting Up New Instances Of The Agents Without Installing The Agent Software

    3.5.4 Setting Up New Instances of the Agents without Installing the Agent Software There are two steps to setting up new instances of the agents without installing the agent software: “Creating New Startup Files” on page 54 “Modifying Existing Load and Unload Scripts” on page 54 Creating New Startup Files Each MTA startup file is named after the domain it services, with a extension.
  • Page 55 3 Following the pattern of the existing commands, add commands for the new load load instances of the agents you are setting up. Use Ctrl+C to copy and Ctrl+V to paste lines in the load script page. The results would be similar to the following example: 4 Click Apply to save the modified load script.

  • Page 56: Testing Your Clustered Groupwise System

    9 Click OK to save the modified properties. 10 In the Cluster State View, take the GroupWise volume offline and then bring it online again to test the new startup files and the modified load and unload scripts. If you need assistance with these tasks, see Section 3.6, “Testing Your Clustered GroupWise System,”...

  • Page 57: Managing Your Clustered Groupwise System

    Section 3.7.1, “Updating GroupWise Objects with Cluster-Specific Descriptions,” on page 57 Section 3.7.2, “Using Novell Remote Manager on NetWare 6.5,” on page 58 Section 3.7.3, “Knowing What to Expect in MTA and POA Failover Situations,” on page 61 3.7.1 Updating GroupWise Objects with Cluster-Specific...

  • Page 58: Using Novell Remote Manager On Netware 6.5

    “Knowing What to Expect in MTA and POA Failover Situations” on page 3.7.2 Using Novell Remote Manager on NetWare 6.5 On NetWare 6.5, you can use Novell Remote Manager to manage many aspects of your GroupWise cluster from your Web browser. For instructions on setting up and accessing this useful network administration utility, see the NetWare 6.5 Novell Remote Manager Administration Guide at the...
  • Page 59 The Cluster Configuration page displays the cluster name, the nodes in the cluster, and the resources in the cluster. It also enables you to create new GroupWise Volume Resource objects (termed Cluster Volumes in the Novell Remote Manager interface). 2 Click the cluster name to display the Cluster object properties: Click a linked item to edit the Cluster object properties.
  • Page 60 Cluster Volume object. Managing Your GroupWise Cluster On the main Novell Remote Manager page: 1 In the left frame, scroll down to the Clustering section, then click Cluster Management. The Cluster Status page displays the nodes and volume resources in the cluster. The master node in the cluster is marked with a yellow ball.

  • Page 61: Knowing What To Expect In Mta And Poa Failover Situations

    To take the currently running volume resource offline, click Offline. To migrate the volume resource, select a node from the drop-down list, then click Migrate. 4 On the Cluster Resource page, click Event Log to view a list of cluster events. The event log can help you resolve problems with cluster functioning.

  • Page 62: Clustering Quick Checklists

    Connecting your clustered GroupWise system to other e-mail systems through GroupWise gateways. See Chapter 6, “Implementing GroupWise Gateways in a NetWare Cluster,” on page 103. Monitoring the status of your clustered GroupWise system from your Web browser. See Chapter 7, “Monitoring a GroupWise System in a NetWare Cluster,” on page 105.

  • Page 63: Domain Quick Checklist

    “Setting the Failover Path and Policies for the Agents” on page Test your new clustered GroupWise system. Section 3.6, “Testing Your Clustered GroupWise System,” on page Record cluster-specific information in the properties pages of the GroupWise objects that the information pertains to. Section 3.7, “Managing Your Clustered GroupWise System,”...

  • Page 64: Post Office Quick Checklist

    Record cluster-specific information in the properties pages of the GroupWise objects that the information pertains to. Section 3.7, “Managing Your Clustered GroupWise System,” on page 3.9.3 Post Office Quick Checklist Plan your new clustered post office. Section 2.4, “Planning a New Clustered Post Office,” on page Cluster-enable the volume where the post office will reside.
  • Page 65 Record cluster-specific information in the properties pages of the GroupWise objects that the information pertains to. Section 3.7, “Managing Your Clustered GroupWise System,” on page Setting Up a Domain and Post Office in a NetWare Cluster...
  • Page 66 GroupWise 8 Interoperability Guide...

  • Page 67: Implementing The Internet Agent In A Netware Cluster

    Implementing the Internet Agent in a NetWare Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 2, “Planning GroupWise in a NetWare Cluster,” on page 21 Chapter 3, “Setting Up a Domain and Post Office in a NetWare Cluster,”...

  • Page 68: Planning A Domain For The Internet Agent

    4.1.1 Planning a Domain for the Internet Agent The considerations involved in planning a domain for the Internet Agent are much the same as planning any other domain. In preparation, review “Planning a New Domain”, then print and fill out “Domain Worksheet”...

  • Page 69: Agent And Its Mta

    INTERNET AGENT CLUSTERING WORKSHEET Under Item 3: Internet Agent Failover Path, list the nodes that you want to have in the Internet Agent volume failover path. 4.1.4 Planning a Secondary IP Address and Cluster-Unique Port Numbers for the Internet Agent and Its MTA As with the MTA and the POA, the Internet Agent needs a secondary IP address and cluster-unique port numbers.

  • Page 70: Deciding Where To Install The Internet Agent And Its Mta

    If the Internet Agent has a large number of nodes on its failover path, you could configure the Internet Agent to send outgoing messages to a relay host, which would then send them out through the firewall using its own IP address rather than the address of the particular node where the Internet Agent was running.

  • Page 71: Planning The Mta Installation

    1 Complete the cluster-enabling steps in the applicable section of the cluster documentation for your version of NetWare, as listed in Chapter 1, “Introduction to GroupWise 8 and Novell Cluster Services on NetWare,” on page The Internet Agent Clustering Worksheet provides the volume to cluster-enable, the cluster- enabled volume IP address, and the failover path for the Internet Agent volume.

  • Page 72: Creating A Domain For The Internet Agent

    ® If you have installed the latest version of ConsoleOne and the Novell Cluster Services snap- in, you can rename the cluster-related objects in case your DNS name server cannot resolve object names that include the underscore (_) character. 2 To ensure successful short name resolution, add entries for the Internet Agent virtual server to support your preferred methods of short name resolution, as described in “Configuring Short...
  • Page 73 2 If you selected on Internet Agent Volume as the Internet Agent installation vol:\system location (Internet Agent Clustering Worksheet item 6), create the directory on vol:\system the Internet Agent volume accessed in Step If you selected on Each Node, decide which node you will install the Internet sys:\system Agent to first, then map a drive to on that node.
  • Page 74 To set up the load script: 1 In ConsoleOne, browse to and select the Cluster object. If necessary, click View > Console View to display its contents. 2 Right-click the Volume Resource object (volume_SERVER), then click Properties > Load to display the default volume resource load script for the Internet Agent volume.
  • Page 75 The result would look similar to the following example: NOTE: The commands are needed in the load script only when the MTA and the Internet Agent are not running in protected memory. The address space parameters are needed in the commands only when the MTA and the Internet Agent are running in protected memory.
  • Page 76 If your system seems to be trying to kill the address space before the Internet Agent and its MTA have been completely unloaded, resulting in the agents hanging in the unloading state, set a delay of several seconds before issuing the unload kill address space command to allow the Internet Agent and its MTA adequate time to unload completely.
  • Page 77 If you are considering changing these defaults, see the applicable section about failover and failback modes in the cluster documentation for your version of NetWare, as listed in Chapter 1, “Introduction to GroupWise 8 and Novell Cluster Services on NetWare,” on page 5 Click OK when you are finished editing the Internet Agent volume resource properties.
  • Page 78 Enabling Internet Addressing for Your Clustered GroupWise System Setting up Internet addressing for a clustered Internet Agent is no different from setting it up for an Internet Agent in a any other environment. Follow the instructions in “Enabling Internet Addressing” in “System” in the GroupWise 8 Administration Guide, then return to this point.

  • Page 79: Testing The Clustered Internet Agent

    Verifying Post Office Links In the Internet Agent object properties pages: 1 Click Post Office Links. 2 Verify that the Access Mode column displays C/S (for client/server mode) for all post offices serviced by the Internet Agent. 3 Verify that the Links column displays the secondary IP addresses of the GroupWise volumes where post offices reside, not the IP addresses of any physical servers in the cluster.

  • Page 80: Managing The Internet Agent In A Cluster

    Internet Agent volume resource online permanently. On NetWare 6.5, these actions can also be performed from your Web browser. See “Using Novell Remote Manager on NetWare 6.5” on page 7 Continue with Managing the Internet Agent in a Cluster.

  • Page 81: Updating Groupwise Objects With Cluster-Specific Descriptions

    4.3.1 Updating GroupWise Objects with Cluster-Specific Descriptions After installing the Internet Agent in your clustered GroupWise system, while the cluster-specific information is fresh in your mind, you should record that cluster-specific information as part of the GroupWise objects in ConsoleOne so that you can easily refer to it later. Be sure to update the information recorded in the GroupWise objects if the configuration of your system changes.

  • Page 82: Knowing What To Expect In An Internet Agent Failover Situation

    4.3.2 Knowing What to Expect in an Internet Agent Failover Situation The failover behavior of the MTA for the Internet Agent domain is the same as for an MTA in a regular domain. See “Knowing What to Expect in MTA and POA Failover Situations” on page Failover of the Internet Agent itself is more complex.

  • Page 83: Internet Agent Quick Checklist

    Item Explanation 5) MTA Network Information: Gather the MTA network address information from the Internet Agent section of the “IP Address Worksheet” on page MTA IP address For more information, see “Planning a Secondary IP Address and MTA message transfer port Cluster-Unique Port Numbers for the Internet Agent and Its MTA”...
  • Page 84 Set up the MTA for the new Internet Agent domain. Section 4.2.3, “Installing the MTA for the Internet Agent Domain,” on page Install the Internet Agent. “Installing the Internet Agent Software in a Cluster” on page Modify the Internet Agent volume resource load script: Remove the command trustmig...

  • Page 85: Implementing Webaccess In A Netware Cluster

    Implementing WebAccess in a NetWare Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 2, “Planning GroupWise in a NetWare Cluster,” on page 21 Chapter 3, “Setting Up a Domain and Post Office in a NetWare Cluster,”...

  • Page 86: Planning A New Domain For The Webaccess Agent

    Section 5.2.2, “Deciding Whether to Cluster-Enable the WebAccess Agent Volume,” on page 86 Section 5.2.3, “Determining an Appropriate Failover Path for the WebAccess Agent Volume,” on page 87 Section 5.2.4, “Planning a Secondary IP Address and Cluster-Unique Port Numbers for the WebAccess Agent and Its MTA,”...

  • Page 87: Determining An Appropriate Failover Path For The Webaccess Agent Volume

    Cluster-enabling relies on successful short name resolution throughout your system. Review Section 2.7, “Ensuring Successful Name Resolution for GroupWise Volumes,” on page 27, which describes the issues in the context of planning MTA and POA installations. 5.2.3 Determining an Appropriate Failover Path for the WebAccess Agent Volume As with the MTA and the POA, you need to decide which nodes in the cluster are appropriate locations where the WebAccess Agent volume could fail over.

  • Page 88: Deciding Whether To Run The Webaccess Agent And Its Mta In Protected Memory

    WEBACCESS CLUSTERING WORKSHEET Under Item 5: MTA Installation Location Item 7: WebAccess Agent Installation Location, mark whether you will install the WebAccess Agent and its MTA to on each node in the sys:\system cluster or to a directory on the WebAccess Agent volume. Also specify where the MTA vol:\system startup file will be stored.

  • Page 89: Setting Up Webaccess In A Cluster

    1 Complete the cluster-enabling steps in the applicable section of cluster documentation for your version of NetWare, as listed in Chapter 1, “Introduction to GroupWise 8 and Novell Cluster Services on NetWare,” on page Implementing WebAccess in a NetWare Cluster...

  • Page 90: Creating A Domain For The Webaccess Agent

    The WebAccess Clustering Worksheet provides the volume to cluster-enable, the cluster- enabled volume IP address, and the failover path for the WebAccess volume. For a review of the new Novell eDirectory objects that are created when you cluster-enable a shared volume, see Section 2.6, “Deciding Whether to Cluster-Enable the Shared Volumes...
  • Page 91 Installing the WebAccess Agent Software in a Cluster The WebAccess Agent is the component of your WebAccess installation that accesses post offices and libraries to retrieve information for WebAccess client users. 1 Map a drive to the WebAccess Agent volume (WebAccess Clustering Worksheet item where the WebAccess domain is located.
  • Page 92 Configuring the WebAccess Agent Volume Resource to Load and Unload the WebAccess Agent and Its MTA The properties of the Volume Resource object define how the WebAccess Agent volume functions within the cluster, how NLM programs are loaded and unloaded, and how failover and failback situations are handled.
  • Page 93 Add a delay so that the MTA is fully loaded before the WebAccess Agent starts to load: load delay delay 10 The length of the delay varies from system to system; ten seconds is a good starting place. Transfer the WebAccess Agent command from the file located in the load...
  • Page 94 Modifying the Volume Resource Unload Script for the WebAccess Agent The volume resource unload script executes whenever the WebAccess Agent volume goes offline. Programs should be unloaded in the reverse order of how they were loaded. This ensures that supporting programs are not unloaded before programs that rely on them in order to function properly.
  • Page 95 3 Click Apply to save the unload script. 4 If necessary, click OK to confirm that you must offline and then online the volume resource in order for the changes to take effect. 5 Continue with Setting the Failover Path and Policies for the WebAccess Agent.

  • Page 96: Testing Your Clustered Webaccess Installation

    NetWare, as listed in Chapter 1, “Introduction to GroupWise 8 and Novell Cluster Services on NetWare,” on page 5 Click OK when you are finished editing the WebAccess Agent volume resource properties.

  • Page 97: Managing Webaccess In A Cluster

    5.4 Managing WebAccess in a Cluster After you have installed WebAccess in a cluster, you should consider some long-term management issues. Section 5.4.1, “Updating GroupWise Objects with Cluster-Specific Descriptions,” on page 97 Section 5.4.2, “Knowing What to Expect in WebAccess Failover Situations,” on page 98 Section 5.4.3, “Updating the WebAccess Agent Configuration File (commgr.cfg),”...

  • Page 98: Knowing What To Expect In Webaccess Failover Situations

    It is also automatically copied to the following Web server subdirectory: sys:\novell\webaccess If you change WebAccess agent configuration information (for example, if you change its ip address), the information is changed in the following file: domain\wpgate\webac80a\commgr.cfg...

  • Page 99: Webaccess Clustering Worksheet

    WebAccess Application failover path are not currently available for update. therefore, you must manually copy the updated file to the subdirectory on each commgr.cfg sys:\novell\webaccess node in the WebAccess Application failover path. 5.5 WebAccess Clustering Worksheet Item Explanation 1) Shared Volume for...

  • Page 100: Webaccess Quick Checklist

    Item Explanation 7) WebAccess Agent Gather the WebAccess Agent network address information from the Network Information: WebAccess section of the “IP Address Worksheet” on page For more information, see “Planning a Secondary IP Address and WebAccess Agent IP Cluster-Unique Port Numbers for the WebAccess Agent and Its MTA” address on page WebAccess Agent HTTP...
  • Page 101 Modify the WebAccess Agent volume resource unload script: Add the MTA and WebAccess Agent or address space command(s) unload Remove the command trustmig “Modifying the Volume Resource Unload Script for the WebAccess Agent” on page Set up the WebAccess Agent volume failover path and policies. “Setting the Failover Path and Policies for the WebAccess Agent”...
  • Page 102 102 GroupWise 8 Interoperability Guide...

  • Page 103: Implementing Groupwise Gateways In A Netware Cluster

    Implementing GroupWise Gateways in a NetWare Cluster ® A significant system configuration difference between a GroupWise system in a clustering environment and a GroupWise system in a regular environment is that you need to create a separate domain to house each GroupWise gateway. The gateway domain should be created on a cluster- enabled volume.
  • Page 104 104 GroupWise 8 Interoperability Guide...

  • Page 105: Monitoring A Groupwise System In A Netware Cluster

    Monitoring a GroupWise System in a NetWare Cluster ® ® Because the GroupWise 8 Monitor currently runs on Windows and Linux, rather than NetWare you cannot run GroupWise Monitor in a NetWare cluster. However, GroupWise Monitor can easily monitor a clustered GroupWise system from a vantage point outside the NetWare cluster. When you first install Monitor, it gathers information about agents to monitor from a domain database ( ).
  • Page 106 106 GroupWise 8 Interoperability Guide...

  • Page 107: Backing Up A Groupwise System In A Netware Cluster

    Backing Up a GroupWise System in a NetWare Cluster ® The GroupWise Target Service Agent for File Systems (TSAFSGW) is a GroupWise-specific API that works with compatible backup software to provide reliable backups of a running GroupWise ® system on NetWare 6.5.
  • Page 108 TSAFSGW connects to the virtual server from all nodes in the cluster. If the node where TSAFSGW is performing a backup goes down, that node is dismounted and the next node is mounted to the virtual server. TSAFSGW on the next node is aware of this and notifies your backup software. Your backup software acknowledges the disruption and attempts to reconnect to the next node.

  • Page 109: Updating A Groupwise System In A Netware Cluster

    Updating a GroupWise System in a NetWare Cluster ® ® In a NetWare cluster, you have the option of installing the GroupWise software on each node in the cluster or on a GroupWise volume along with a domain or post office, as described in Section 2.8.3, “Deciding Where to Install the Agent Software,”...
  • Page 110 110 GroupWise 8 Interoperability Guide...

  • Page 111: Moving An Existing Groupwise 8 System Into A Netware Cluster

    If you are adding the high availability benefits of Novell Cluster Services to a GroupWise system that is already up and running, the first step is to install Novell Cluster Services following the ® instructions in the clustering documentation for your version of NetWare...
  • Page 112 Take care of the cluster management details described in Section 3.7, “Managing Your Clustered GroupWise System,” on page Move more domains and post offices into the cluster as needed. If you have GroupWise libraries, see Section 2.5, “Planning a New Library for a Clustered Post Office,” on page Move GroupWise administration into the cluster as needed.

  • Page 113: Implementing Messenger In A Netware Cluster

    Implementing Messenger in a NetWare Cluster ® Novell Messenger does not require the existence of a GroupWise system in the cluster, but presumably one has already been set up as described in Chapter 2, “Planning GroupWise in a NetWare Cluster,” on page 21 Chapter 3, “Setting Up a Domain and Post Office in a NetWare...

  • Page 114: Deciding Where To Install The Messenger Agent Software

    MESSENGER CLUSTERING WORKSHEET Under Item 6: Installation Location for Messenger Administration, mark where you want to install the Messenger snap-in to ConsoleOne. If you plan to install the Messenger snap-in to ConsoleOne on a cluster-enabled shared volume, under Item 7: Shared Volume for Messenger Administration, list the IP address of the shared volume and the directory where you want to install the Messenger snap-in.
  • Page 115 Each Node in the Cluster Make sure you have filled out item 5 on the Messenger Clustering Worksheet with a complete list of nodes in the cluster. Skip to “Planning the Messenger Agent Installation” on page 116. Shared Volume For convenience throughout the rest of this section, the term “Messenger volume” means “a cluster- enabled shared volume where the Messenger agents are installed.”...

  • Page 116: Setting Up Your Messenger System In A Cluster

    Yes. This adds the /cluster switch to the agent startup files. The /cluster switch tells the Messenger agents to use the virtual server name of the cluster or the Messenger volume rather than the specific server name in pathnames obtained from agent object properties in Novell eDirectory or from startup switches.

  • Page 117: Installing To Each Node In The Cluster

    “Starting the Messenger Installation Program” and “Creating Your Messenger System” in “Installing a Novell Messenger System” in the Messenger 2.0 Installation Guide. Make each node in the cluster active to make sure that the Messenger agents start successfully. 11.2.2 Installing to a Messenger Volume Complete the following tasks to set up your Messenger system on a Messenger volume: “Preparing the Cluster for Messenger”...
  • Page 118 Messenger system, following the steps provided in “Starting the Messenger Installation Program” and “Creating Your Messenger System” in “Installing a Novell Messenger System” in the Messenger 2.0 Installation Guide. Keep in mind the following cluster-specific details: When you specify the Messenger installation directory, be sure to browse to the location...
  • Page 119 11 Click Policies to display the default start, failover, and failback policies. By default, a volume resource: Fails over automatically if the node it is running on fails Starts automatically on the net node in its failover path Continues running at its failover location even after its most preferred node is again available 12 Change the policies if necessary, then click OK.
  • Page 120 Messenger volume resource online permanently. On NetWare 6.5, these actions can also be performed from your Web browser. See “Using Novell Remote Manager on NetWare 6.5” on page 120 GroupWise 8 Interoperability Guide...

  • Page 121: Messenger Clustering Worksheet

    Section 2.1, “Meeting Software Version Requirements,” on page 2) eDirectory Tree for Cluster: Record the eDirectory tree where you created the Novell Cluster object when you installed Novell Cluster Services. To review the background information provided for GroupWise clustering, see Section 2.2, “Installing Novell Cluster Services,”...
  • Page 122 Item Explanation 7) Shared Volume for Messenger If you plan to install the Messenger snap-in to ConsoleOne on Administration: a shared volume, specify the name (cluster_volume) of the shared volume where you will install it. Cluster Volume IP Address: Specify the IP addresses of the virtual server Installation Location for Messenger (volume_SERVER.cluster) to which the shared volume is tied.
  • Page 123 Novell Cluster Services on Linux Chapter 12, “Introduction to GroupWise 8 and Novell Cluster Services on Linux,” on page 125 Chapter 13, “Planning GroupWise in a Linux Cluster,” on page 127 Chapter 14, “Setting Up a Domain and a Post Office in a Linux Cluster,” on page 137 Chapter 15, “Implementing the Internet Agent in a Linux Cluster,”...
  • Page 124 124 GroupWise 8 Interoperability Guide...

  • Page 125: Introduction To Groupwise 8 And Novell Cluster Services On Linux

    GroupWise system: cluster: A grouping of from two to 32 servers configured using Novell Cluster Services so that data storage locations and applications can transfer from one server to another without interrupting their availability to users.
  • Page 126 cluster resource: A shared partition, secondary IP address, application, service, Web server, etc., that can function successfully anywhere in the cluster. Cluster resources include the GroupWise agents and the Messenger agents. failover: The process of moving cluster resources from a failed node to a functional node so that availability to users is uninterrupted.

  • Page 127: Planning Groupwise In A Linux Cluster

    System in a Linux Cluster,” on page 215) is designed for those who are creating a new GroupWise ® system, or at least new domains and post offices, in the context of Novell Cluster Services Linux. If you already have an existing GroupWise 8 system on OES Linux and need to configure it to work in a newly installed cluster, see Chapter 20, “Moving an Existing Linux GroupWise 8 System into a...

  • Page 128: Installing Novell Cluster Services On Linux

    IMPORTANT: Cluster-enabling is required for GroupWise. Mounting the shared partitions where you want to set up GroupWise domains and post offices. As you install Novell Cluster Services on Linux, record key information about the cluster on the System Clustering Worksheet:...

  • Page 129: Planning A Clustered Software Distribution Directory

    Parts of your GroupWise system can run in one cluster while other parts of it run in one or more other clusters. Parts of your GroupWise system can run in a cluster while other parts run outside of the cluster, on non-clustered servers.

  • Page 130: Planning A New Clustered Domain

    SYSTEM CLUSTERING WORKSHEET If you want to have your GroupWise software distribution directory as part of your cluster, under Item 6: GroupWise Partition for Software Distribution Directory, list the GroupWise partition and associated secondary IP address for the software distribution directory. List the full path for the software distribution directory, regardless of whether it is located on a GroupWise partition or on each node in the cluster.

  • Page 131: Planning A New Clustered Post Office

    13.4 Planning a New Clustered Post Office The considerations involved in planning a new post office in a clustering environment are essentially the same as for any other environment. The initial post office in a new GroupWise system is planned on the Basic GroupWise System Worksheet. To plan additional new post offices, review “Planning a New Post Office ”, then print and fill out the...

  • Page 132: Deciding How To Install And Configure The Linux Agents In A Cluster

    13.6 Deciding How to Install and Configure the Linux Agents in a Cluster There are several cluster-specific issues to consider as you plan to install the Linux MTA and POA in your clustered GroupWise system: Section 13.6.1, “Recording Secondary IP Addresses for the Agents,” on page 132 Section 13.6.2, “Determining Appropriate Failover Lists for the Agents,”...

  • Page 133: Groupwise Clustering Worksheets

    AGENT CLUSTERING WORKSHEET Under Item 2: Domain Failover List, list the nodes that you want to have in the domain partition failover list. The MTA might need to run on any node that the domain partition fails over to. Therefore, you will install the agent software on all of the nodes in the domain failover list.

  • Page 134: System Clustering Worksheet

    13.7.1 System Clustering Worksheet Item Explanation 1) eDirectory Tree for Cluster: Record the eDirectory tree where you created the new Novell Cluster object when you installed Novell Cluster Services. For more information, see Section 13.1, “Installing Novell Cluster Services on Linux,” on page 128...

  • Page 135: Agent Clustering Worksheet

    Item Explanation 8) GroupWise Partition for Post Office: Specify the name of the shared partition where the GroupWise post office will reside and its secondary IP address. Secondary IP Address: For more information, see Section 13.4, “Planning a New Clustered Post Office,” on page 131.
  • Page 136 Item Explanation 6) POA Network Information: Record the POA network address information for the server where the POA will run. The POA IP address is the same as POA IP address the post office secondary IP address in the cluster. POA client/server port Section 13.6.1, “Recording Secondary IP Addresses for POA message transfer port...

  • Page 137: Setting Up A Domain And A Post Office In A Linux Cluster

    2 Make sure that ConsoleOne is installed on the node. If necessary, you can download ConsoleOne for Linux from the Novell Product Downloads site (http://download.novell.com). ConsoleOne is always installed in /usr/Consoleone 3 If necessary, mount the GroupWise partition where you want to create the GroupWise software...

  • Page 138: Creating A New Secondary Domain In A Linux Cluster

    IMPORTANT: Do not select the Configure GroupWise for Clustering option at this time. 6 When you set up the software distribution directory, install all the agent software. Although this is not required when creating your initial domain and post office, it makes installation of the other GroupWise agents easier after you have created the initial domain and post office.

  • Page 139: Creating A New Post Office In A Linux Cluster

    7 Rebuild the domain database for the new domain, following the steps provided in “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 8 Administration Guide. The database rebuild is necessary in order to transfer the MTA configuration information and the domain link information into the secondary domain database, because the MTA for the new domain is not yet running.

  • Page 140: Installing And Configuring The Mta And The Poa In A Cluster

    9 Rebuild the post office database for the new post office, following the steps provided in “Rebuilding Domain or Post Office Databases” in “Databases” in the GroupWise 8 Administration Guide. Be sure to browse to the database location (under System Clustering Worksheet item 11) through the GroupWise partition.
  • Page 141 Running the GroupWise Installation Program on the Preferred Node 1 Mount the GroupWise partition for the domain (System Clustering Worksheet item 7) or the post office (System Clustering Worksheet item 2 From the software distribution directory you created in Step 6 Section 14.1, “Setting Up a New GroupWise System in a Linux Cluster,”...
  • Page 142 GroupWise 8 Installation Guide: “Running the Linux GroupWise Agents As a Non-root User” “Setting Up Non-root Access on an NSS Volume on Novell Open Enterprise Server Linux” 6 Continue with Running the GroupWise Installation Program on Subsequent Nodes. Running the GroupWise Installation Program on Subsequent Nodes...
  • Page 143 ( ) is created in the gwha.conf /etc/opt/novell/ directory. It is configured specifically for the agents you just selected. groupwise Because the agent startup files and log files are stored on the shared resource, they do not need to be customized for each cluster node.

  • Page 144: Changing Agent Paths To Locations On Groupwise Partitions

    GroupWise 8 Installation Guide: “Running the Linux GroupWise Agents As a Non-root User” “Setting Up Non-root Access on an NSS Volume on Novell Open Enterprise Server Linux” 7 Repeat Step 1 through Step 6 for each cluster node in the GroupWise agent failover list.
  • Page 145 Setting the MTA Message Log File Path If you plan to enable message logging, as described in “Enabling MTA Message Logging” in “Message Transfer Agent” in the GroupWise 8 Administration Guide: 1 On the GroupWise partition where the domain is located, create the directory where you want to store MTA message log files.

  • Page 146: Configuring Groupwise Cluster Resources To Load And Unload The Agents

    The cluster resource load script executes whenever the GroupWise partition comes online. On OES Linux, all cluster management activities are performed in Novell iManager. To set up the load script in iManager: 1 Expand Clusters, then click Cluster Options. 2 In the Cluster field, browse to the Cluster object where the GroupWise cluster resource is located.
  • Page 147 4 Select the GroupWise Cluster Resource object that you created when you set up the GroupWise partition, then click Properties. The default load script from a generic IP service template appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # mount the file system exit_on_error mount -t reiserfs /dev/evms/vol /mnt/generic # add the IP address exit_on_error add_secondary_ipaddress a.b.c.d...
  • Page 148 . /opt/novell/ncs/lib/ncsfunc # define the IP address RESOURCE_IP=123.123.1. # define the file system type MOUNT_FS=reiserf # define the device exit_on_error evms -f /var/opt/novell/ncs/ContainerActivate -rl Share ‘uname -n‘ MOUNT_DEV=/dev/evms/Share/dat # define the mount point MOUNT_POINT=/mnt/mount_point # mount the file system exit_on_error mount -t $MOUNT_FS $MOUNT_DEV $MOUNT_POINT...
  • Page 149 1 On the Cluster Resource Properties page of the GroupWise cluster resource, click Scripts > Unload Script. The default unload script appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # request service stop ignore_error /etc/init.d/myservice stop # stop service otherwise sleep 8...
  • Page 150 /mnt/generic load script. The result would be similar to the following: 3 If this is a traditional Linux volume, use the following unload script: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs /etc/init.d/grpwise stop domain /etc/init.d/grpwise stop post_office.domain # define the IP address RESOURCE_IP=172.16.5.18 150 GroupWise 8 Interoperability Guide...
  • Page 151 # define the mount point MOUNT_POINT=/mnt/mount_point sleep 8 ignore_error fuser -k $MOUNT_POINT # del the IP address ignore_error del_secondary_ipaddress $RESOURCE_IP # umount the file system exit_on_error umount $MOUNT_POINT # return status exit 0 Make the following changes to set up the unload script for the agents. 3a Use the following command to stop the MTA: /etc/init.d/grpwise stop domain 3b Use the following command to stop the POA:...

  • Page 152: Setting Up New Instances Of The Agents Without Installing The Agent Software

    “Setting Start, Failover, and Failback Modes” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. 2 Under Preferred Nodes, arrange the nodes in the cluster into the desired failover list for the domain or post office (under Agent Clustering Worksheet items 3 or 3 Click OK.
  • Page 153 4 Save the new startup file. 5 Edit the GroupWise High Availability service configuration file ( /etc/opt/novell/ groupwise/gwha.conf 6 Make a copy of the section for an existing domain and its MTA or post office and its POA, then modify the information for the new domain or post office and its accompanying agent.

  • Page 154: Testing Your Clustered Groupwise System

    9 Change other Cluster Resource properties as needed. 10 Click OK to save the modified properties. 11 In the Cluster Manager, take the GroupWise partition offline and then bring it online again to test the new startup files and the modified load and unload scripts. If you need assistance with these tasks, see Testing Your Clustered GroupWise System.

  • Page 155: Managing Your Clustered Groupwise System

    3 Select the cluster node where you want to online the GroupWise cluster resource, then click After a moment, the GroupWise cluster resource displays Running in the State column. 4 At the server where the MTA and/or POA are starting, use the following command to see if they are running: /etc/init.d/grpwise status domain /etc/init.d/grpwise status post_office.domain...
  • Page 156 6 In the Description field of the MTA Identification page, record the secondary IP address of the domain’s GroupWise partition. This information appears on the MTA server console, no matter which node in the cluster it is currently running on. 7 Click Apply to save the description.

  • Page 157: Knowing What To Expect In Mta And Poa Failover Situations

    Recording Cluster-Specific Information for a Software Distribution Directory To permanently record important cluster-specific information about a software distribution directory located on a GroupWise partition: 1 In ConsoleOne, click Tools > System Operations > Software Directory Management. 2 Select the software distribution directory, then click Edit. 3 In the description field, record the secondary IP address of the GroupWise partition where the software distribution directory resides.

  • Page 158: Clustering Quick Checklists

    Monitoring the status of your clustered GroupWise system from your Web browser. See Chapter 17, “Implementing GroupWise Monitor in a Linux Cluster,” on page 201. Backing up your clustered GroupWise system. See Chapter 18, “Backing Up a GroupWise System in a Linux Cluster,” on page 215.

  • Page 159: Post Office Quick Checklist

    Modify the domain cluster resource load script. “Modifying the Cluster Resource Load Script for the Agents” on page 146. Modify the domain cluster resource unload script. “Modifying the Cluster Resource Unload Script for the Agents” on page 149. Set up the domain failover list and policies. “Setting the Failover List and Policies for the Agents”...
  • Page 160 160 GroupWise 8 Interoperability Guide...

  • Page 161: Implementing The Internet Agent In A Linux Cluster

    Implementing the Internet Agent in a Linux Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 13, “Planning GroupWise in a Linux Cluster,” on page 127 Chapter 14, “Setting Up a Domain and a Post Office in a Linux Cluster,”...

  • Page 162: Planning A Domain For The Internet Agent

    15.1.1 Planning a Domain for the Internet Agent The considerations involved in planning a domain for the Internet Agent are much the same as planning any other domain. In preparation, review “Planning a New Domain”, then print and fill out “Domain Worksheet”...

  • Page 163: Determining An Appropriate Failover List For The Internet Agent

    15.1.3 Determining an Appropriate Failover List for the Internet Agent By default, a GroupWise partition is configured to have all nodes in the cluster in its failover list, organized in ascending alphanumeric order. Only one node at a time can have a particular GroupWise partition mounted and active.

  • Page 164: Planning The Mta Installation

    Standard Ports Table 15-1 Protocol Standard Port IMAP4 LDAP POP3 SMTP By default, the Internet Agent sends outgoing messages on the primary IP address of the server where it is running. If you decide to use this default configuration, your firewall must be configured to allow outbound TCP/IP traffic from all nodes in the Internet Agent partition failover list.

  • Page 165: Setting Up The Internet Agent In A Linux Cluster

    15.2 Setting Up the Internet Agent in a Linux Cluster You should already have reviewed Section 15.1, “Planning the Internet Agent in a Linux Cluster,” on page 161 and filled out Section 15.5, “Internet Agent Clustering Worksheet,” on page 178. You are now ready to complete the following tasks to set up the Internet Agent in a clustering environment: Section 15.2.1, “Creating a Domain for the Internet Agent,”...
  • Page 166 Installing and Setting Up the Internet Agent Software in Your Cluster The Internet Agent must be installed on each node in its failover list (Internet Agent Clustering Worksheet item “Running the Internet Agent Installation Program on the Preferred Node” on page 166 “Running the Internet Agent Installation Program on Subsequent Nodes”...
  • Page 167 GroupWise 8 Installation Guide: “Running the Linux GroupWise Agents As a Non-root User” “Setting Up Non-root Access on an NSS Volume on Novell Open Enterprise Server Linux” 7 Continue with Running the Internet Agent Installation Program on Subsequent Nodes.
  • Page 168 The GroupWise High Availability service is automatically configured on the current cluster node and its configuration file ( ) is created in the gwha.conf /etc/opt/novell/ directory. It is configured specifically for the agents you just selected. groupwise 168 GroupWise 8 Interoperability Guide...
  • Page 169 GroupWise 8 Installation Guide: “Running the Linux GroupWise Agents As a Non-root User” “Setting Up Non-root Access on an NSS Volume on Novell Open Enterprise Server Linux” 7 Repeat Step 1 through Step 6 for each cluster node in the Internet Agent failover list.
  • Page 170 4 Select the Internet Agent cluster resource that you created when you set up the Internet Agent partition, then click Properties. The default load script from a generic IP service template appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # mount the file system exit_on_error mount -t reiserfs /dev/evms/vol /mnt/generic 170 GroupWise 8 Interoperability Guide...
  • Page 171 . /opt/novell/ncs/lib/ncsfunc # define the IP address RESOURCE_IP=123.123.1. # define the file system type MOUNT_FS=reiserf # define the device exit_on_error evms -f /var/opt/novell/ncs/ContainerActivate -rl Share ‘uname -n‘ MOUNT_DEV=/dev/evms/Share/dat # define the mount point MOUNT_POINT=/mnt/mount_point # mount the file system exit_on_error mount -t $MOUNT_FS $MOUNT_DEV $MOUNT_POINT...
  • Page 172 1 On the Cluster Resource Properties page of the Internet Agent cluster resource, click Scripts > Unload Script. The default unload script appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # request service stop ignore_error /etc/init.d/myservice stop # stop service otherwise sleep 8...
  • Page 173 /mnt/generic load script. 3 If this is a traditional Linux volume, use the following unload script: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs /etc/init.d/grpwise stop domain.gwia /etc/init.d/grpwise stop domain # define the IP address RESOURCE_IP=172.16.5.18 # define the mount point...
  • Page 174 “Setting Start, Failover, and Failback Modes” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. 2 Under Preferred Nodes, arrange the nodes in the cluster into the desired failover list for the Internet Agent (Internet Agent Clustering Worksheet item 3 Click OK.

  • Page 175: Testing The Internet Agent In A Linux Cluster

    2 Verify the contents of the Hostname/DNS “A Record” Name field. It displays the hostname as currently configured in DNS. It should display the hostname that corresponds to the secondary IP address of the Internet Agent cluster resource. For more information, see Section 15.1.5, “Preparing DNS for the Clustered Internet Agent,”...
  • Page 176 The new Internet Agent cluster resource shows Offline in the State column. 2 Click the new Internet Agent cluster resource, then click Online. 3 Select the cluster node where you want to online the Internet Agent cluster resource, then click After a moment, the Internet Agent cluster resource displays Running in the State column.

  • Page 177: Managing The Internet Agent In A Linux Cluster

    15.4 Managing the Internet Agent in a Linux Cluster After you have installed the Internet Agent in a cluster, you should consider some long-term management issues. Section 15.4.1, “Updating GroupWise Objects with Cluster-Specific Descriptions,” on page 177 Section 15.4.2, “Knowing What to Expect in an Internet Agent Failover Situation,” on page 178 15.4.1 Updating GroupWise Objects with Cluster-Specific Descriptions...

  • Page 178: Knowing What To Expect In An Internet Agent Failover Situation

    3 In the Description field, record the secondary IP address of the GroupWise partition where the Internet Agent domain is located. This information appears on the Internet Agent console, no matter which node in the cluster it is currently running on. 4 Click OK to save the Internet Agent information.

  • Page 179: Internet Agent Quick Checklist

    Item Explanation 5) MTA Network Information: Record the MTA network address information that you will need as you install the MTA. MTA IP address For more information, see Section 15.1.7, “Planning the MTA MTA message transfer port Installation,” on page 164.
  • Page 180 Section 15.3, “Testing the Internet Agent in a Linux Cluster,” on page 175. Record cluster-specific information in the properties pages of the GroupWise objects associated with the Internet Agent. Section 15.4.1, “Updating GroupWise Objects with Cluster-Specific Descriptions,” on page 177. 180 GroupWise 8 Interoperability Guide...

  • Page 181: Implementing Webaccess In A Linux Cluster

    Implementing WebAccess in a Linux Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 13, “Planning GroupWise in a Linux Cluster,” on page 127 Chapter 14, “Setting Up a Domain and a Post Office in a Linux Cluster,”...

  • Page 182: Planning A Domain For The Webaccess Agent

    Section 16.6, “WebAccess Agent Clustering Worksheet,” on page 197 lists the information you need as you set up the WebAccess Agent in a clustering environment. You should print the worksheet and fill it out as you complete the tasks listed below: Section 16.2.1, “Planning a Domain for the WebAccess Agent,”...

  • Page 183: Selecting The Webaccess Agent Partition And Secondary Ip Address

    16.2.2 Selecting the WebAccess Agent Partition and Secondary IP Address As with the MTA and the POA, the WebAccess Agent needs a secondary IP address that remains the same no matter which node in the cluster it is running on. You can place the WebAccess Agent and its domain on a GroupWise partition where a domain or post office already reside, which means...

  • Page 184: Planning The Mta Installation

    WEBACCESS AGENT CLUSTERING WORKSHEET Under Item 4: Cluster Resource Mount Point, list the mount point for the GroupWise partition where the WebAccess Agent domain is located. 16.2.5 Planning the MTA Installation Follow the instructions in Section 13.6.4, “Planning the Linux Agent Installation,” on page 133, then return to this point.

  • Page 185: Creating A Domain For The Webaccess Agent

    16.3.1 Creating a Domain for the WebAccess Agent The WebAccess Agent domain will be a secondary domain. To create it, follow the instructions in Section 14.2, “Creating a New Secondary Domain in a Linux Cluster,” on page 138, taking your information from the WebAccess Agent Clustering Worksheet, rather than the System Clustering Worksheet, then return to this point.
  • Page 186 Availability service is automatically configured and its configuration file ( ) is gwha.conf created in the directory. If another GroupWise agent has /etc/opt/novell/groupwise already been installed on this cluster node, the file is updated to include the gwha.conf WebAccess Agent.
  • Page 187 file in the subdirectory of the software distribution clusterimport.conf gwinst directory from which you ran the GroupWise Installation program is updated, so that the cluster-specific information collected when you configured the WebAccess Agent on the preferred node is available when you install the WebAccess Agent on subsequent nodes. The WebAccess Agent is not configured to start automatically on system startup.
  • Page 188 GroupWise 8 Installation Guide. /opt/novell/groupwise/agents/bin/gwinter --show @webac80a.waa & 2 Stop the WebAccess Agent by closing the window that it is running in. 3 After you can see that the WebAccess Agent stopped successfully, test it by starting it as a daemon, as described in “Starting the Linux GroupWise Agents as...
  • Page 189 5 Repeat Step 1 through Step 4for each node in the WebAccess Agent failover list. 6 Continue with “Configuring Clustered Logging” on page 189 Configuring Clustered Logging The default location for the WebAccess Agent log files is on the cluster nodes along with the WebAccess Agent software, rather than being located with the domain on the WebAccess Agent partition.
  • Page 190 4 Select the WebAccess Agent cluster resource that you created when you set up the WebAccess Agent partition, then click Properties. The default load script from a generic IP service template appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # mount the file system exit_on_error mount -t reiserfs /dev/evms/vol /mnt/generic # add the IP address exit_on_error add_secondary_ipaddress a.b.c.d...
  • Page 191 . /opt/novell/ncs/lib/ncsfunc # define the IP address RESOURCE_IP=123.123.1. # define the file system type MOUNT_FS=reiserf # define the device exit_on_error evms -f /var/opt/novell/ncs/ContainerActivate -rl Share ‘uname -n‘ MOUNT_DEV=/dev/evms/Share/dat # define the mount point MOUNT_POINT=/mnt/mount_point # mount the file system exit_on_error mount -t $MOUNT_FS $MOUNT_DEV $MOUNT_POINT...
  • Page 192 1 On the Cluster Resource Properties page of the WebAccess Agent cluster resource, click Scripts > Unload Script. The default unload script appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # request service stop ignore_error /etc/init.d/myservice stop # stop service otherwise sleep 8...
  • Page 193 “Setting Start, Failover, and Failback Modes” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. 2 Under Preferred Nodes, arrange the nodes in the cluster into the desired failover list for the WebAccess Agent (WebAccess Agent Clustering Worksheet item 3 Click OK.

  • Page 194: Installing And Configuring The Webaccess Application In A Cluster

    Verifying WebAccess Agent Object Properties During installation of the WebAccess Agent, the WebAccess Agent object should have been configured correctly. However, it can be helpful to verify certain cluster-specific information in order to familiarize yourself with the configuration of a clustered WebAccess Agent. “Accessing WebAccess Agent Object Properties”...

  • Page 195: Testing The Webaccess Agent In A Linux Cluster

    16.4 Testing the WebAccess Agent in a Linux Cluster After you have configured the WebAccess Agent cluster resource, you can test the load and unload scripts by bringing the cluster resource online and taking it offline again. 1 In iManager, expand Clusters, then click Cluster Manager. The new WebAccess Agent cluster resource shows Offline in the State column.

  • Page 196: Managing The Webaccess Agent In A Linux Cluster

    /etc/init.d/grpwise status webac80a 5 Select the new WebAccess Agent cluster resource, then click Offline. The State column for the WebAccess Agent cluster resource returns to Offline. 6 Use the same command that you used in Step 4 to verify that the WebAccess Agent has stopped.

  • Page 197: Knowing What To Expect In A Webaccess Agent Failover Situation

    This information appears on the MTA console, no matter which node in the cluster it is currently running on. 7 Click OK to save the MTA description. 8 Continue with Recording Cluster-Specific Information about the WebAccess Agent. Recording Cluster-Specific Information about the WebAccess Agent With the contents of the WebAccess Agent domain still displayed: 1 Right-click the WebAccess Agent object, then click Properties.

  • Page 198: Webaccess Agent Quick Checklist

    Item Explanation 2) WebAccess Agent Specify a unique name for the Internet Agent domain. Specify the Domain Name: directory on the GroupWise partition where you want to create the new domain. Domain Database Location: For more information, see Section 16.2.1, “Planning a Domain for the WebAccess Agent,”...
  • Page 199 Modify the WebAccess Agent cluster resource unload script. “Modifying the Cluster Resource Unload Script for the WebAccess Agent and Its MTA” on page 192. Set up the WebAccess Agent failover list and policies. “Setting the Failover List and Policies for the WebAccess Agent and Its MTA” on page 193.
  • Page 200 200 GroupWise 8 Interoperability Guide...

  • Page 201: Implementing Groupwise Monitor In A Linux Cluster

    Implementing GroupWise Monitor in a Linux Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 13, “Planning GroupWise in a Linux Cluster,” on page 127 Chapter 14, “Setting Up a Domain and a Post Office in a Linux Cluster,”...

  • Page 202: Planning Groupwise Monitor In A Linux Cluster

    17.2 Planning GroupWise Monitor in a Linux Cluster A major system configuration difference between the Monitor Agent and other GroupWise agents is that the Monitor Agent needs access to a domain during installation but does not need permanent access to a domain thereafter. Section 17.6, “Monitor Agent Clustering Worksheet,”...

  • Page 203: Selecting The Monitor Agent Partition And Secondary Ip Address

    17.2.3 Selecting the Monitor Agent Partition and Secondary IP Address As with the MTA and the POA, the Monitor Agent needs a secondary IP address that remains the same no matter which node in the cluster it is running on. You can associate the Monitor Agent with the domain that was accessed during installation or with any other domain, so that they fail over together, or you can associate the Monitor Agent with its own shared partition, so that it fails over independently of any domain.

  • Page 204: Planning The Monitor Agent Installation

    17.2.6 Planning the Monitor Agent Installation Aside from the cluster-specific issues discussed in the preceding sections, the considerations involved in planning to install the Monitor Agent are the same in a clustering environment as for any other environment. Review the installation instructions in “Installing the Linux Monitor Agent”...
  • Page 205 4 Install the Monitor Agent software, following the steps provided in “Installing the Linux Monitor Agent” in “Installing GroupWise Monitor” in the GroupWise 8 Installation Guide. 5 Configure the Monitor Agent, following the steps provided in “Configuring the Linux Monitor Agent”...

  • Page 206: Configuring The Monitor Agent Cluster Resource To Load And Unload The Monitor

    2 From the software distribution directory you created in Step 6 Section 14.1, “Setting Up a New GroupWise System in a Linux Cluster,” on page 137, start the GroupWise Installation program and select Configure GroupWise for Clustering. 3 Install the Monitor Agent software on the cluster node as usual, but do not use the Configure option.

  • Page 207: Agent

    Monitor Agent partition, then click Properties. The default load script from a generic IP service template appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # mount the file system exit_on_error mount -t reiserfs /dev/evms/vol /mnt/generic # add the IP address exit_on_error add_secondary_ipaddress a.b.c.d # start the service exit_on_error /etc/init.d/myservice start...
  • Page 208 . /opt/novell/ncs/lib/ncsfunc # define the IP address RESOURCE_IP=123.123.1. # define the file system type MOUNT_FS=reiserf # define the device exit_on_error evms -f /var/opt/novell/ncs/ContainerActivate -rl Share ‘uname -n‘ MOUNT_DEV=/dev/evms/Share/dat # define the mount point MOUNT_POINT=/mnt/mount_point # mount the file system exit_on_error mount -t $MOUNT_FS $MOUNT_DEV $MOUNT_POINT...
  • Page 209 1 On the Cluster Resource Properties page of the Monitor Agent cluster resource, click Scripts > Unload Script. The default unload script appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # request service stop ignore_error /etc/init.d/myservice stop # stop service otherwise sleep 8...
  • Page 210 “Setting Start, Failover, and Failback Modes” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. 2 Under Preferred Nodes, arrange the nodes in the cluster into the desired failover list for the Monitor Agent (Monitor Agent Clustering Worksheet item 3 Click OK.

  • Page 211: Testing The Monitor Agent In A Linux Cluster

    17.4 Testing the Monitor Agent in a Linux Cluster After you have configured the Monitor Agent cluster resource, you can test the load and unload scripts by bringing the Monitor Agent cluster resource online and taking it offline again. 1 In iManager, expand Clusters, then click Cluster Manager. The new Monitor Agent cluster resource shows Offline in the State column.

  • Page 212: Managing The Monitor Agent In A Linux Cluster

    5 Select the new Monitor Agent cluster resource, then click Offline. The State column for the Monitor Agent cluster resource returns to Offline. 6 Use the same command that you used in Step 4 to verify that the Monitor Agent has stopped. 7 Repeat Step 2 whenever you are ready to bring the new Monitor Agent cluster resource online...

  • Page 213: Monitor Agent Quick Checklist

    17.7 Monitor Agent Quick Checklist Plan the new clustered Monitor Agent, including a domain to access during installation to gather information about agents to monitor Section 17.2, “Planning GroupWise Monitor in a Linux Cluster,” on page 202. Install the Monitor Agent on all nodes in the Monitor Agent’s failover list. Section 17.3.1, “Installing and Configuring the Monitor Agent on Each Node in Your Cluster,”...
  • Page 214 214 GroupWise 8 Interoperability Guide...

  • Page 215: Backing Up A Groupwise System In A Linux Cluster

    Backing Up a GroupWise System in a Linux Cluster ® To back up GroupWise data in a Linux cluster, you can use the GroupWise Database Copy (DBCopy) utility to copy the data from the live GroupWise system to a static location for backup. For more information, see “Backing Up GroupWise Databases”...
  • Page 216 216 GroupWise 8 Interoperability Guide...

  • Page 217: Updating A Groupwise System In A Linux Cluster

    Updating a GroupWise System in a Linux Cluster ® In a Linux cluster, you must install the GroupWise software on each node in the cluster. Before you run the GroupWise Installation program to install updated software, make sure you know all the cluster nodes where the GroupWise software is already installed.
  • Page 218 218 GroupWise 8 Interoperability Guide...

  • Page 219: Moving An Existing Linux Groupwise 8 System Into A Linux Cluster

    If you are adding the high availability benefits of Novell Cluster Services to a GroupWise system that is already up and running, the first step is to install Novell Cluster Services following the instructions in OES Novell Cluster Services 1.8.2 Administration Guide for Linux.
  • Page 220 Chapter 17, “Implementing GroupWise Monitor in a Linux Cluster,” on page 201 Chapter 18, “Backing Up a GroupWise System in a Linux Cluster,” on page 215 220 GroupWise 8 Interoperability Guide...

  • Page 221: Moving A Clustered Groupwise 8 System From Netware To Linux

    NetWare Cluster to Linux” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. It is possible to have a cluster that includes both NetWare and ® Linux servers. Therefore, you can move your GroupWise 8 system from NetWare servers to Linux servers one component at a time.
  • Page 222 222 GroupWise 8 Interoperability Guide...

  • Page 223: Implementing Messenger In A Linux Cluster

    Implementing Messenger in a Linux Cluster ® Novell Messenger does not require the existence of a GroupWise system in the cluster, but presumably one has already been set up as described in Chapter 13, “Planning GroupWise in a Linux Cluster,” on page 127 Chapter 14, “Setting Up a Domain and a Post Office in a Linux...

  • Page 224: Selecting The Messenger Partition And Secondary Ip Address

    22.1.2 Selecting the Messenger Partition and Secondary IP Address If you are not planning to enable archiving, or if you are not anticipating a large Messenger archive, you can use one Messenger partition for both the Messaging Agent and the Archive Agent. If you anticipate archiving a large number of messages so that the Messenger archive grows very large, you might want to have a separate Messenger partition for the Archive Agent and its archive database.

  • Page 225: Planning The Messenger Agent Installation

    Aside from the cluster-specific issues discussed in the preceding sections, the considerations involved in planning to install the Messenger agents are the same in a clustering environment as for any other environment. Review “Planning Your Novell Messenger System”, then print and fill out “Novell Messenger Worksheet”...
  • Page 226 If your cluster uses NSS volumes, as described in “Creating NSS Volumes” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux, you must set up non- access to those NSS volumes, as described in “Setting Up Non-root Access on an NSS...

  • Page 227: Changing Messenger Paths To Locations On The Messenger Partition

    Messenger partition. ® 2 In ConsoleOne , browse to and select the Novell Messenger Service object (MessengerService), then click Messenger Server > Archive Agent. 3 Right-click the File Module object, then click Properties. 4 In the Store Path field, specify your archive store path, then click OK.
  • Page 228 1 Choose a directory for the Messaging Agent queue and create that directory on the Messenger partition. 2 In ConsoleOne, browse to and select the Novell Messenger Service object (MessengerService), then click Messenger Server. 3 Right-click the Messaging Agent object, then click Properties.

  • Page 229: Configuring The Messenger Cluster Resource To Load And Unload The Messenger

    4 Select the Messenger cluster resource that you created when you set up the Messenger partition, then click Properties. The default load script from a generic IP service template appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # mount the file system exit_on_error mount -t reiserfs /dev/evms/vol /mnt/generic # add the IP address exit_on_error add_secondary_ipaddress a.b.c.d...
  • Page 230 . /opt/novell/ncs/lib/ncsfunc # define the IP address RESOURCE_IP=123.123.1. # define the file system type MOUNT_FS=reiserf # define the device exit_on_error evms -f /var/opt/novell/ncs/ContainerActivate -rl Share ‘uname -n‘ MOUNT_DEV=/dev/evms/Share/dat # define the mount point MOUNT_POINT=/mnt/mount_point # mount the file system exit_on_error mount -t $MOUNT_FS $MOUNT_DEV $MOUNT_POINT...
  • Page 231 1 On the Cluster Resource Properties page of the Monitor Agent cluster resource, click Scripts > Unload Script. The default unload script appears as follows: #!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # request service stop ignore_error /etc/init.d/myservice stop # stop service otherwise sleep 8...
  • Page 232 “Setting Start, Failover, and Failback Modes” in “Installation and Setup” in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux. 2 Under Preferred Nodes, arrange the nodes in the cluster into the desired failover list for the Messenger agents (under Messenger Clustering Worksheet item 3 Click OK.

  • Page 233: Testing Your Clustered Messenger System

    After a moment, the Messenger cluster resource displays Running in the State column. 4 At the server where the Messenger agents are starting, use the following commands to see that the Messenger agents have started: /etc/init.d/novell-nmma status /etc/init.d/novell-nmaa status 5 Select the new Messenger cluster resource, then click Offline.

  • Page 234: Managing Your Clustered Messenger System

    22.5 Messenger Clustering Worksheet Item Explanation 1) eDirectory Tree for Cluster: Record the eDirectory tree where you created the Novell Cluster object when you installed Novell Cluster Services For more information, see Section 13.1, “Installing Novell Cluster Services on Linux,” on page 128.

  • Page 235: Messenger Clustering Quick Checklist

    5) Shared Partitions in Cluster: List the shared partitions that are available for use in your Messenger system. For more information, see Section 13.1, “Installing Novell Cluster Services on Linux,” on page 128. 6) Messenger Partition for Messaging The Messaging Agent software is installed on each node in its...
  • Page 236 Section 22.2.2, “Changing Messenger Paths to Locations on the Messenger Partition,” on page 227. Modify the Messenger agents cluster resource load script. “Modifying the Cluster Load Script for the Messenger Agents” on page 229. Modify the Messenger agents cluster resource unload script. “Modifying the Cluster Resource Unload Script for the Messenger Agents”...

  • Page 237: Part Iii Novell Teaming And Conferencing

    Novell Teaming and Conferencing documentation Web site (http://www.novell.com/documentation/ team_plus_conf). These guides provide detailed product installation and configuration instructions, but they do not include specific instructions for integrating Novell Teaming 2.0 or Conferencing 1.0 ® with eDirectory or GroupWise .
  • Page 238 238 GroupWise 8 Interoperability Guide...

  • Page 239: Using Groupwise With Novell Teaming

    23.1 Understanding How Novell Teaming Interacts with eDirectory and GroupWise When you install Novell Teaming in an environment where eDirectory and GroupWise are already set up, the products interact in the following ways: Teaming can use eDirectory for LDAP authentication of Teaming users. This means that you do not need to create Teaming users manually.

  • Page 240: Enabling Groupwise/Teaming Integration For Groupwise Windows Client Users

    Novell Teaming 2.0 Administration Guide: “Configuring E-Mail Integration” For e-mail usage instructions, see the following sections of the Novell Teaming 2.0 Advanced User Guide: “Sending E-Mail to Team Members and Announcing the Workspace After Its Creation” in “Creating and Managing Workspaces”...
  • Page 241 6 Click OK. By providing the Teaming site URL in ConsoleOne, you provide GroupWise Windows client users with the functionality described in Section 23.5.1, “Accessing Teaming through the Novell Teaming Folder,” on page 242. Using GroupWise with Novell Teaming 241...

  • Page 242: Accessing Teaming From The Groupwise Client

    RSS feed, if a calendar and RSS feed are available for the team. When users subscribe to a team RSS feed, a My Team Feeds folder is created under the Novell Teaming folder.

  • Page 243: Using Groupwise With Conferencing

    Section 24.1.1, “Preparing for GroupWise Integration with Conferencing,” on page 243 Section 24.1.2, “Integrating GroupWise with Novell Conferencing,” on page 243 Section 24.1.3, “Testing GroupWise as the Novell Conferencing E-Mail System,” on page 244 24.1.1 Preparing for GroupWise Integration with Conferencing...

  • Page 244: Testing Groupwise As The Novell Conferencing E-Mail System

    7b Specify the password for the username, then press Enter. 8 Continue as usual with the Conferencing installation. 24.1.3 Testing GroupWise as the Novell Conferencing E-Mail System 1 Make sure that users receive the Conferencing Welcome e-mail, as described in “Installing the...

  • Page 245: Streamlining Authentication To Teaming Or Conferencing

    You can implement single sign-on for use with Teaming or Conferencing. Section 25.1, “Using iChain for Authenticating to Teaming or Conferencing,” on page 245 Section 25.2, “Using Novell Access Manager for Authenticating to Teaming or Conferencing,” on page 247 25.1 Using iChain for Authenticating to Teaming or Conferencing ®...

  • Page 246: Consoleone

    For example, you might want to call it Teaming or Conferencing, as appropriate. 4 Select Allow Pages to Be Cached at the Browser. 5 Select Enable Multi-Homing. 5a In the Multi-Homing Options dialog box, select Domain-Based Multi-Homing to configure the Teaming or Conferencing URL as a DNS name prepended to your Internet domain name, for example: http://teaming.yourcompanyname.com The A record for the DNS name must already exist.

  • Page 247: Using Ichain For Authentication

    Teaming or Conferencing in a single step, using their eDirectory or LDAP passwords. 25.2 Using Novell Access Manager for Authenticating to Teaming or Conferencing Novell Access Manager is not currently supported for use with Novell Teaming or Conferencing. Streamlining Authentication to Teaming or Conferencing 247...
  • Page 248 248 GroupWise 8 Interoperability Guide...

  • Page 249: Part Iv Novell Zenworks

    Novell ZENworks Chapter 26, “Using ZENworks Desktop Management to Distribute the GroupWise Windows Client,” on page 251 Chapter 27, “Using ZENworks Linux Management to Distribute the GroupWise Linux/Mac Client,” on page 259 Chapter 28, “ZENworks Application Virtualization for GroupWise and Messenger,” on...
  • Page 250 250 GroupWise 8 Interoperability Guide...

  • Page 251: Using Zenworks Desktop Management To Distribute The Groupwise Windows Client

    Using ZENworks Desktop Management to Distribute the GroupWise Windows Client ® You can use the Application Management functionality in Novell ZENworks Desktop Management to distribute the GroupWise Windows client to workstations. The following sections provide instructions: Section 26.1, “Creating a GroupWise Client Application Object,” on page 251 Section 26.2, “Using GroupWise 8 Tuner,”...
  • Page 252 3 Select An Application that Has an .msi File, then click Next to display the file path page. .msi 4 In the Path to .msi File field, browse for and select the file. groupwise.msi 5 Click Next to display the Application object information page, then customize the object name, source path, and target path information if necessary.
  • Page 253 Object Name: The name to be used for the Application object in eDirectory. You might want to use a descriptive name. Administration Package Path: The directory from which the GroupWise client will be installed. Specify the full path to the client directory (for example, ).
  • Page 254 Novell ZENworks Documentation Web site (http://www.novell.com/documentation-index/ index.jsp?category=ZENworks). After you associate the Application objects with the users you want, Novell Application Launcher displays the Application object’s icon on the users’ workstations, if the workstation meets the operating system requirements. If the Application object’s icon does not appear immediately, have the user refresh Novell Application Launcher.

  • Page 255: Using Groupwise 8 Tuner

    C:\Program Files user. You must install the GroupWise client to an unprotected area such as, C:\Novell\GroupWise if you are using a non-Administrator user. 1 From the directory of the GroupWise 8 or greater download,...
  • Page 256 7 Select if you want to add GroupWise to the client Startup folder. 8 Select if you want to install GroupWise Internet Browser Mail Integration. 9 Click Next to continue. 10 Select the languages to install, then click Next. 11 Select the default startup language for the client, then click Next. 12 Select which software integration you want the client to use.

  • Page 257: Configuring Zenworks To Use A Transform File

    13 Click Finish to create the transform file ( ) in the client software distribution groupwise.mst directory. 26.3 Configuring ZENworks to Use a Transform File After you have created the transform file ( ), you must configure ZENworks to use groupwise.mst the transform file when doing MSI installations.
  • Page 258 258 GroupWise 8 Interoperability Guide...

  • Page 259: Using Zenworks Linux Management To Distribute The Groupwise Linux/Mac Client

    Using ZENworks Linux Management to Distribute the GroupWise Linux/Mac Client You can install the GroupWise Linux/Mac client and agents using Novell ZENworks Linux Management or later. Refer to the Novell ZENworks Linux Management (http://www.novell.com/ products/zenworks/linuxmanagement/) site for additional information. Using ZENworks Linux Management to Distribute the GroupWise Linux/Mac Client...
  • Page 260 260 GroupWise 8 Interoperability Guide...

  • Page 261: Zenworks Application Virtualization For Groupwise And Messenger

    For instructions on virtualizing the GroupWise Windows client, see “Preparing GroupWise and GroupWise Notify for Virtualization” in the ZENworks Integration Guide (http://www.novell.com/ documentation/zav61/zav61_integration/data/index.html). For instructions on virtualizing the Messenger Windows client, see “Preparing GroupWise Messenger for Virtualization” in the ZENworks Integration Guide (http://www.novell.com/...
  • Page 262 262 GroupWise 8 Interoperability Guide...

  • Page 263: Part V Other Novell Products

    Other Novell Products Chapter 29, “GroupWise DirXML Driver for Novell Identity Manager,” on page 265 Chapter 30, “GroupWise Customization Tools,” on page 269 Chapter 31, “Novell exteNd,” on page 271 Other Novell Products...
  • Page 264 264 GroupWise 8 Interoperability Guide...

  • Page 265: Groupwise Dirxml Driver For Novell Identity Manager

    Section 29.1.9, “Enabling the DirXML Warnings,” on page 267 29.1.1 Recovering a Deleted GroupWise Account 1 Using the DirXML Management role in Novell iManager, stop the GroupWise DirXML driver. 2 Recover the deleted account, as described in “Recovering Deleted GroupWise Accounts”...

  • Page 266: Grafting Users

    3 Using the DirXML Management role, restart the GroupWise DirXML driver. 29.1.4 Converting a User to an External Entity 1 On the DirXML tab of the User object in Novell iManager, disable the association with the GroupWise DirXML driver. 2 Convert the user, as described in “Convert User to External...

  • Page 267: Resolving An Invalid Association

    29.1.7 Resolving an Invalid Association 1 On the DirXML tab of the User object in Novell iManager, disable the association with the GroupWise DirXML driver. 2 Resolve the invalid association, as described in “Invalid Associations” in “System” in the GroupWise 8 Administration Guide.
  • Page 268 268 GroupWise 8 Interoperability Guide...

  • Page 269: Groupwise Customization Tools

    (such as C++). It also supports COM Automation, which is an industry standard for interfacing applications. For more information, see GroupWise Administrative Object API (http://developer.novell.com/wiki/index.php/ GroupWise_Administrative_Object_API). GroupWise C3PO (Custom 3rd-Party Object): Works with C++, Delphi, or Visual Basic to let you add menu and toolbar items to trigger applications.
  • Page 270 The GroupWise WSDL (Service Descriptive Language) combines everything into a GroupWise Web service. For more information, see GroupWise Web Service (SOAP) (http:/ /developer.novell.com/wiki/index.php/GroupWise_Web_Service_%28SOAP%29). GroupWise MAPI: Uses a set of object-oriented functions that provide messaging capabilities. The Messaging Application Programming Interface (MAPI) is used by mail- enabled applications to create, transfer, and store messages, as well as to handle complex addressing information.

  • Page 271: Novell Extend

    GroupWise 8 directory. Refer to the Identity Manager Accessory Portlet Reference Guide (http://developer.novell.com/wiki/index.php/ GroupWise_Controls_for_ActiveX) to determine which exteNd template files you should copy to directory. Do not copy the entire contents of the previous directory into the GroupWise 8 directory;...
  • Page 272 272 GroupWise 8 Interoperability Guide...
  • Page 273 Microsoft Clustering Services on Windows Chapter 32, “Introduction to GroupWise 8 and Microsoft Clusters,” on page 275 Chapter 33, “Planning GroupWise in a Microsoft Cluster,” on page 277 Chapter 34, “Setting Up a Domain and Post Office in a Microsoft Cluster,” on page 293 Chapter 35, “Implementing the Internet Agent in a Microsoft Cluster,”...
  • Page 274 274 GroupWise 8 Interoperability Guide...

  • Page 275: Introduction To Groupwise 8 And Microsoft Clusters

    Introduction to GroupWise 8 and Microsoft Clusters ® Before implementing GroupWise 8 in a Microsoft* cluster, make sure you have a solid understanding of Microsoft clustering technologies by reviewing the following information resources: Windows Server 2008 – High Availability (http://www.microsoft.com/windowsserver2008/en/ us/high-availability.aspx) Windows Server 2003 –...
  • Page 276 another resource group consisting of a post office and its POA, and a third resource group for WebAccess, each resource group could be configured to fail over separately to different nodes in the cluster. failback: The process of returning resources and resource groups to their original node after the situation causing the failover has been resolved.

  • Page 277: Planning Groupwise In A Microsoft Cluster

    Planning GroupWise in a Microsoft Cluster The majority of this part of the guide (Chapter 33, “Planning GroupWise in a Microsoft Cluster,” on page 277 through Chapter 39, “Backing Up a GroupWise System in a Microsoft Cluster,” on ® page 331) is designed for those who are creating a new GroupWise system, or at least new domains and post offices, in a Microsoft cluster.

  • Page 278: Setting Up Your Microsoft Cluster

    33.1 Setting Up Your Microsoft Cluster As you set up your Microsoft cluster, record key information about the cluster on the System Clustering Worksheet: SYSTEM CLUSTERING WORKSHEET Under Item 1: Cluster Name, record the name of your Microsoft cluster. Under Item 2: Nodes in Cluster, list the servers that you have added to the cluster.

  • Page 279: Planning A New Clustered Post Office

    System Summary Sheet” in “Installing a Basic GroupWise System” in the GroupWise 8 Installation Guide. This covers planning the primary domain and an initial post office in the primary domain. Secondary Domain: If your GroupWise system already exists, you will be creating a new secondary domain.

  • Page 280: Planning A New Library For A Clustered Post Office

    33.4 Planning a New Library for a Clustered Post Office The considerations involved in planning a library in a Microsoft cluster are essentially the same as for any other environment. You can plan a library for a new clustered post office by following the standard instructions provided in “Creating and Managing Libraries”...

  • Page 281: Planning Shared Administrative Resources

    If a resource group’s current owner node fails, the resource group fails over to the next node in the possible owners list. You should customize the owners list for each GroupWise resource group based on the fan-out-failover principle. When a node fails, its resource groups should not all fail over together to the same node in the cluster.
  • Page 282 A client program (such as ConsoleOne) that runs on a Windows workstation, can be configured to use several different short name resolution methods. To see which methods are in use at a particular ® workstation, view the protocol preferences for the Novell Client that is installed on the Windows...

  • Page 283: Deciding How To Install And Configure The Agents In A Cluster

    For short name resolution to work using DNS, the client workstation must either belong to the same DNS zone (such as support.novell.com) as the resource group, or the cluster resource zone must be configured in the client’s DNS suffix search path under TCP/IP settings for the workstation.
  • Page 284 The following filled-out version of the Network Address Worksheet illustrates one way this can be done: Domain Information Domain IP Address MTP Port HTTP Port Provo1 172.16.5.81 7100 7180 Post Office Information Post Office IP Address C/S Port MTP Port HTTP Port Development (same as MTA)

  • Page 285: Deciding Where To Install The Agent Software

    The example uses default port numbers where possible. For example, the default MTA message transfer port is 7100 and the default POA client/server port is 1677. Incrementing port numbers are used in the example when multiple components have the same type of ports. For example, port numbers 1677 and 1678 are both POA client/server ports and port numbers 7180 through 7184 are all HTTP ports.
  • Page 286 Because the agents must be installed as Windows services in a Microsoft cluster, you must initially run the Agent Installation program for each node in the cluster so that the Windows services for the agents get created, regardless of where you are planning to run the agents from. However, for updates, you need to run the Agent Installation program only once if you are running the agents from a shared disk.

  • Page 287: Planning The Agent Services

    Even if you choose to install the agents to the directory of multiple nodes, you can still c:\grpwise store the agent startup files on shared disks with the domains and post offices. The significant advantage of this approach is that you only have one startup file to modify per agent. AGENT CLUSTERING WORKSHEET Under Item 1: Agent Installation...

  • Page 288: Groupwise Clustering Worksheets

    GROUPWISE AGENT INSTALLATION WORKSHEET Under Agents and Locations, mark POA Local to Post Office and MTA Local to Domain. In a Microsoft cluster, a domain or post office and its agent must be located on the same node in order to fail over together.
  • Page 289 Item Explanation 3) Resources for GroupWise List any shared locations that you want to set up for Administration: ConsoleOne or the software distribution directory. ConsoleOne: For more information, see Section 33.6, “Planning Shared Administrative Resources,” on page 281. Shared disk: Possible owners: Software Distribution Directory: Shared disk:...

  • Page 290: Network Address Worksheet

    Item Explanation 9) Document Storage Area Location: If you need a library for a clustered post office, mark where you want to create its document storage area and provide a At the post office directory if necessary. Outside the post office For more information, see Section 33.4, “Planning a New Separate post office...

  • Page 291: Agent Clustering Worksheet

    WebAccess Information WebAccess WebAccess WebAccess WebAccess Agent IP Address MTP Port HTTP Port Agent Port HTTP Port WebAccess Domain MTA WebAccess (same) Agent (GWINTER) 33.9.3 Agent Clustering Worksheet Item Explanation 1) Agent installation location: Mark the location where you will install the agent software. If necessary, specify the location where you will store agent Shared disk with domain or post startup files on the same shared disk with the domain or post...
  • Page 292 Item Explanation 7) POA Network Information: Gather the POA network address information from the “Network Address Worksheet” on page 290. POA IP address For more information, see “Planning Cluster-Unique Port POA client/server port Numbers for Agents in the Cluster” on page 283.

  • Page 293: Setting Up A Domain And Post Office In A Microsoft Cluster

    Setting Up a Domain and Post Office in a Microsoft Cluster You should have already reviewed “Planning GroupWise in a Microsoft Cluster” on page 277 filled out the “System Clustering Worksheet” on page 288, the “Network Address Worksheet” on page 290, and the “Agent Clustering Worksheet”...

  • Page 294: Configuring Short Name Resolution

    ® ® ConsoleOne uses Novell eDirectory to resolve the UNC path of a domain or post office directory into its network name in the cluster. For example, on the workstation where you run ConsoleOne, you need to map a drive to the location of a domain directory using the network name of the domain resource group so that ConsoleOne can access the domain database no matter which node in the cluster it is active on.

  • Page 295: Setting Up A New Groupwise System In A Cluster

    34.2 Setting Up a New GroupWise System in a Cluster The GroupWise Installation Advisor walks you through setting up the primary domain and an initial post office in the primary domain. You might be creating your primary domain and initial post office in the same resource group or in two different resource groups.

  • Page 296: Creating A New Secondary Domain In A Cluster

    34.3 Creating a New Secondary Domain in a Cluster After you have set up the primary domain and initial post office, as described in Section 34.2, “Setting Up a New GroupWise System in a Cluster,” on page 295, you can create additional secondary domains as needed.

  • Page 297: Creating A New Post Office In A Cluster

    Although a complete mesh link configuration is the most efficient, it might not be feasible in all situations. Set up as many direct TCP/IP links as possible for best MTA performance in the cluster. 9 Make sure you are still connected to the primary domain. 10 Rebuild the domain database for the new domain, following the steps provided in “Rebuilding Domain or Post Office...

  • Page 298: Installing And Configuring The Mta And The Poa In A Cluster

    5 In ConsoleOne, right-click the new Post Office object, then click Properties. 6 Click GroupWise > Post Office Settings, then in the Access Mode field, select Client/Server Only. 7 Right-click the new POA object, then click Properties. On the POA Agent Settings and Scheduled Events pages, you might want to specify unique times for the following POA activities to prevent multiple POAs from performing the same activities on the same node at the same time during a failover situation: Start User Upkeep...

  • Page 299: Installing The Agent Software In A Cluster

    Under some circumstances, the agent software has already been installed in the cluster and you simply need to create a new startup file specific to the new domain or post office. For example: You have created a new domain and/or post office in a GroupWise resource group where the agent software is already installed in the directory for the resource group.

  • Page 300: Editing Clustered Agent Startup Files

    7 If you installed the agent software to each node and you selected Yes for Consolidate Startup Files? (under Agent Clustering Worksheet item 1), copy one complete set of agent startup files to the planned location on the shared disk, then delete all agent startup files from the directories on the nodes to avoid future confusion.

  • Page 301: Testing Your Clustered Groupwise System

    3 Scroll down through the startup file looking for other active (not commented out) startup switches, then modify them as needed for the new instance of the agent. 4 Save the new startup file. 5 Continue with Testing Your Clustered GroupWise System.

  • Page 302: Knowing What To Expect In Mta And Poa Failover Situations

    This information appears on the MTA console, no matter which node in the cluster it is currently running on. 7 Click OK to save the MTA description. 8 Continue with Recording Cluster-Specific Information for a Post Office and Its POA. Recording Cluster-Specific Information for a Post Office and Its POA To permanently record important cluster-specific information for a post office: 1 In ConsoleOne, browse to and right-click the Post Office object, then click Properties.

  • Page 303: What's Next

    Typically, the POA returns to full functionality faster than the MTA. This benefits GroupWise client users, who can reconnect to their mailboxes very quickly and probably do not notice if messages to users in other post offices are not delivered immediately. The only time a user would need to restart the GroupWise client would be if he or she was actually in the process of sending a message when the POA went down.
  • Page 304 304 GroupWise 8 Interoperability Guide...

  • Page 305: Implementing The Internet Agent In A Microsoft Cluster

    Implementing the Internet Agent in a Microsoft Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 33, “Planning GroupWise in a Microsoft Cluster,” on page 277 Chapter 34, “Setting Up a Domain and Post Office in a Microsoft Cluster,”...

  • Page 306: Planning The Internet Agent Resource Group

    Keep in mind the following cluster-specific details: When you specify the location for the domain directory on the Domain Worksheet, include the shared disk where you want the domain directory to be located. Do not concern yourself with the GroupWise agent information on the Domain Worksheet. You can stop with item 10.

  • Page 307: Preparing Your Firewall For The Internet Agent

    INTERNET AGENT CLUSTERING WORKSHEET Under Item 5: MTA Network Information, transfer the resource group IP address and cluster-unique port numbers from the Internet Agent section of the Network Address Worksheet to the Internet Agent Clustering Worksheet. Under Item 7: Internet Agent Network Information, transfer the resource group IP address (the same as for its MTA) and the cluster-unique Internet Agent port number from the Internet Agent section of the Network Address Worksheet to the Internet Agent Clustering Worksheet.

  • Page 308: Planning The Mta Installation

    “Deciding Where to Install the Agent Software” on page 285, which describes the issues in the context of planning MTA and POA installations. As with the MTA and POA, the Internet Agent and its MTA must be installed as Windows services. INTERNET AGENT CLUSTERING WORKSHEET Under Item 4: MTA Installation Location...

  • Page 309: Setting Up The Internet Agent Resource Group

    35.2.1 Setting Up the Internet Agent Resource Group 1 Create the Internet Agent resource group and agent services resources (Internet Agent Clustering Worksheet item 1), as planned in “Planning the Internet Agent Resource Group” on page 306. 2 To ensure successful short name resolution, add entries for the Internet Agent network name to support your preferred methods of short name resolution, as described in “Configuring Short Name Resolution”...
  • Page 310 3 If you plan to install the Internet Agent software to the shared disk of the Internet Agent resource group (Internet Agent Clustering Worksheet item 6), create the directory on the shared disk accessed in Step drive:\grpwise\gwia If you plan to install the Internet Agent software to each node in the cluster, create the directory on the drive accessed in Step c:\grpwise\gwia...
  • Page 311 “Verifying the Reference to the Network Name in Directory Paths” on page 311 “Verifying Post Office Links” on page 311 “Forcing Use of the Internet Agent Resource Group IP Address” on page 312 Accessing Internet Agent Object Properties ® 1 In ConsoleOne , browse to and select the Internet Agent domain in order to display its contents.

  • Page 312: Testing The Clustered Internet Agent

    Forcing Use of the Internet Agent Resource Group IP Address If you want the Internet Agent to send outgoing messages on its resource group IP address, rather than using the default the node IP address: 1 Click GroupWise > Network Address. 2 In the TCP/IP Address field, provide the resource group IP address (Internet Agent Clustering Worksheet item...

  • Page 313: Knowing What To Expect In An Internet Agent Failover Situation

    2 In the Description field of the Internet Agent domain Identification page, provide a cluster- specific description of the Internet Agent domain, including its resource group IP address and the cluster-unique port numbers used by its MTA. 3 Click OK to save the Internet Agent domain description. 4 Select the Internet Agent Domain object to display its contents.

  • Page 314: Internet Agent Clustering Worksheet

    35.4 Internet Agent Clustering Worksheet Item Explanation 1) Resource Group for Internet Specify the information for the Internet Agent resource group. Agent: For more information, see “Planning the Internet Agent Resource Group” on page 306. Network name: IP address: Physical disk: File share: MTA service resource: Internet Agent service resource:...

  • Page 315: Implementing Webaccess In A Microsoft Cluster

    Implementing WebAccess in a Microsoft Cluster ® You should already have set up at least a basic GroupWise system, as described in Chapter 33, “Planning GroupWise in a Microsoft Cluster,” on page 277 Chapter 34, “Setting Up a Domain and Post Office in a Microsoft Cluster,” on page 293.

  • Page 316: Setting Up Your Web Server In The Microsoft Cluster

    Because the WebAccess Application is installed to a subdirectory of the Web server installation directory ( ), the WebAccess Application cannot be installed directory\com\novell\webaccess on a shared disk. Instead, you will install it to each node in the cluster where the Web server has been installed.

  • Page 317: Planning The Webaccess Resource Group

    WEBACCESS CLUSTERING WORKSHEET Under Item 1: Resource Group for WebAccess Agent, transfer the shared disk from the Domain Worksheet to the WebAccess Clustering Worksheet. Under Item 2: WebAccess Agent Domain Name, transfer the domain name and directory from the Domain Worksheet to the WebAccess Clustering Worksheet. 36.2.3 Planning the WebAccess Resource Group The WebAccess resource group is similar to the domain and post office resource groups you have already set up, as described in...

  • Page 318: Deciding Where To Install The Webaccess Agent And Its Mta

    36.2.5 Deciding Where to Install the WebAccess Agent and Its As with the MTA and the POA, you can choose to install the WebAccess Agent and its MTA to each node in the cluster or to the shared disk of the WebAccess resource group. For a discussion of these alternatives, see “Deciding Where to Install the Agent Software”...

  • Page 319: Setting Up Webaccess In A Cluster

    Information, mark the Web server you have installed in your cluster and specify the Web server root directory. Also, specify a directory on the Web server where you want to install the WebAccess Agent configuration file. the default is c:\novell 36.3 Setting Up WebAccess in a Cluster You should already have reviewed “Planning GroupWise in a Microsoft Cluster”...

  • Page 320: Creating A Domain For The Webaccess Agent

    36.3.2 Creating a Domain for the WebAccess Agent The WebAccess Agent domain will be a secondary domain. To create it, follow the instructions in Section 34.3, “Creating a New Secondary Domain in a Cluster,” on page 296, taking your information from the WebAccess Clustering Worksheet, rather than the System Clustering Worksheet, then return to this point.

  • Page 321: Installing And Configuring The Webaccess Application In A Cluster

    On the Gateway Directory page, be sure to browse to the domain directory through the drive you mapped in Step 1 above. On the Execution Options page, be sure that Run WebAccess Agent as a Windows Service is selected. On the Start Applications page, deselect Start the GroupWise WebAccess Agent. 6 Repeat Step 4 Step...

  • Page 322: Testing Your Clustered Webaccess Installation

    6 Make sure you have completed all the WebAccess Application tasks described in “NetWare and Windows: Setting Up GroupWise WebAccess” in “Installing GroupWise WebAccess” in GroupWise 8 Installation Guide. 7 Copy the directory from the server where you just installed the directory\docs\com WebAccess Application to the document root directory of the Web server.

  • Page 323: Updating Groupwise Objects With Cluster-Specific Descriptions

    36.4.1 Updating GroupWise Objects with Cluster-Specific Descriptions After installing WebAccess in your clustered GroupWise system, while the cluster-specific information is fresh in your mind, you should record that cluster-specific information as part of the GroupWise objects in ConsoleOne so that you can easily refer to it later. Be sure to update the information recorded in the GroupWise objects if the configuration of your system changes.

  • Page 324: Knowing What To Expect In Webaccess Failover Situations

    It is also automatically copied to the following Web server subdirectory: drive:\novell\webaccess If you change WebAccess agent configuration information (for example, if you change its IP address), the information is changed in the following file: domain\wpgate\webac80a\commgr.cfg...

  • Page 325: Webaccess Clustering Worksheet

    36.5 WebAccess Clustering Worksheet Item Explanation 1) Resource Group for Specify the information for the WebAccess resource group. WebAccess Agent: For more information, see “Planning the WebAccess Resource Group” on page 317. Group name: Network name: IP address: Shared disk: Share name: MTA service resource: WebAccess Agent service...
  • Page 326 Item Explanation 7) Physical Web Servers: List the servers in the cluster where you are installing the Web server for use with WebAccess. For more information, see “Setting Up Your Web Server in the Microsoft Cluster” on page 316. 8) Web Server Record the secondary IP address for the Web server in the cluster.

  • Page 327: Implementing Groupwise Gateways In A Microsoft Cluster

    Implementing GroupWise Gateways in a Microsoft Cluster ® A significant system configuration difference between a GroupWise system in a clustering environment and a GroupWise system in a regular environment is that you need to create a separate domain to house each GroupWise gateway. The gateway domain should be created in its own resource group.
  • Page 328 328 GroupWise 8 Interoperability Guide...

  • Page 329: Monitoring A Groupwise System In A Microsoft Cluster

    Monitoring a GroupWise System in a Microsoft Cluster ® GroupWise Monitor is similar to WebAccess in that it relies on a Web server for communication with administrators’ Web browsers. Consequently, the setup procedure for GroupWise Monitor in a Microsoft cluster is similar to the setup procedure for WebAccess. If you have set up WebAccess in your clustered GroupWise system, you should already have the skills necessary to set up GroupWise Monitor as well.
  • Page 330 330 GroupWise 8 Interoperability Guide...

  • Page 331: Backing Up A Groupwise System In A Microsoft Cluster

    This means that GroupWise users cannot be logged into their mailboxes while backups are running. To find backup software that is compatible with GroupWise, see the Novell Partner Product Guide (http://www.novell.com/partnerguide). Backing Up a GroupWise System in a Microsoft Cluster...
  • Page 332 332 GroupWise 8 Interoperability Guide...

  • Page 333: Moving An Existing Groupwise 8 System Into A Microsoft Cluster

    Moving an Existing GroupWise 8 System into a Microsoft Cluster ® If you are adding the high availability benefits of a Microsoft cluster to a GroupWise 8 system that is already up and running, the first step is to set up the cluster and review Chapter 32, “Introduction to GroupWise 8 and Microsoft Clusters,”...
  • Page 334 Add other components to your clustered GroupWise system as needed, following the instructions in: Chapter 35, “Implementing the Internet Agent in a Microsoft Cluster,” on page 305 Chapter 36, “Implementing WebAccess in a Microsoft Cluster,” on page 315. Chapter 37, “Implementing GroupWise Gateways in a Microsoft Cluster,” on page 327 Chapter 38, “Monitoring a GroupWise System in a Microsoft Cluster,”...

  • Page 335: Implementing Messenger In A Microsoft Cluster

    Implementing Messenger in a Microsoft Cluster ® ® Novell Messenger does not require the existence of a GroupWise system in your Microsoft cluster, but presumably one has already been set up as described in Chapter 33, “Planning GroupWise in a Microsoft Cluster,” on page 277 Chapter 34, “Setting Up a Domain and Post...

  • Page 336: Deciding Where To Install The Messenger Agent Software

    Windows Messenger Agents, you can choose between two different installation locations: Messenger Agent Software Installation Locations Table 41-1 Location Description Each node in the c:\novell\nm directory is the default installation location provided by the cluster Messenger Installation program. Shared disk If you create a...

  • Page 337: Planning The Messenger Agent Installation

    Messenger Clustering Worksheet. Under Item 13: Configure Agents for Clustering? on the Messenger System Worksheet, mark No. This applies to the Messenger Agents running with Novell Cluster Services , not in a Microsoft cluster. Under Item 14: Admin Configuration...

  • Page 338: Setting Up Your Messenger System In A Cluster

    “Starting the Messenger Installation Program” and “Creating Your Messenger System” in “Installing a Novell Messenger System” in the Messenger 2.0 Installation Guide for each node in the cluster. 2 After you have installed the software to each node in the cluster, if you selected Yes for...

  • Page 339: Messenger Clustering Worksheet

    Installation Guide. 5 Install the Windows Messenger agents, keeping in mind the following cluster-specific details: Use the Novell Messenger System Worksheet that you filled out in “Planning the Messenger Agent Installation” on page 116 to fill in the fields during the Messenger installation process.
  • Page 340 Item Explanation 3) Installation Location for Messenger Mark the location where you will install the Messenger agent Agents: software. For more information, see “Deciding Where to Install the Each node in the cluster Messenger Agent Software” on page 336. Consolidate startup files? Shared disk 4) Resource Group for Messenger If you plan to install the Messenger agent software to a shared...

  • Page 341: Part Vii Non-Groupwise Clients

    Non-GroupWise Clients V I I If your users already have a common POP, IMAP, or SOAP e-mail client that comes with Linux or ® Windows, they can continue to use it to access their GroupWise mailboxes. Users of non- ® GroupWise e-mail clients retain the feature sets of their familiar e-mail clients, but many GroupWise features are not available to such users because they are not offered in POP, IMAP, and...
  • Page 342 342 GroupWise 8 Interoperability Guide...

  • Page 343: Outlook Express

    Outlook Express ® The GroupWise Internet Agent is required in order for users to access their mailboxes using non- GroupWise clients. If you have not already installed the Internet Agent, follow the instructions in GroupWise 8 Installation Guide. In order for users to access their GroupWise mailboxes from a third-party e-mail client, they must configure their e-mail clients to access their GroupWise accounts.
  • Page 344 8 Select My Server Requires Authentication, then click OK. The default setting for server authentication is Use Same Settings as My Incoming Mail Server, so you do not need to change any settings. 9 To access your GroupWise mailbox in Outlook Express, click Tools > Send and Receive. 10 Click the IP address or hostname of your mail server.

  • Page 345: Microsoft Outlook

    Guide, available on the GroupWise 8 Documentation Web site (http:// www.novell.com/documentation/gw8). If your users have been using the Microsoft Outlook e-mail client that comes with Microsoft Office, they can continue to use POP or IMAP in it to access their GroupWise mailboxes.
  • Page 346 6 Provide the e-mail account settings for the type of server you selected. 7 Click Test Account Settings to make sure that you have provided the information correctly. 8 Click Next, then click Finish. You can now access your GroupWise mailbox using Microsoft Outlook by selecting the profile you just created.

  • Page 347: Evolution

    ® ® If you have Evolution 2.4 or later installed, you can access accounts on Novell GroupWise Section 44.1, “GroupWise Features Available in Evolution,” on page 347 Section 44.2, “Configuring Evolution,”...

  • Page 348: Configuring Evolution

    3 On the Identity page, type your e-mail address, then click Forward. 4 On the Receiving Mail page, select Novell GroupWise as your server type. 5 Type the name of your mail server, your user name, and select whether to use SSL.
  • Page 349 6 Click Forward. 7 On the Receive Options page, select if you want Evolution to automatically check for new mail. If you select this option, you need to specify how often Evolution should check for new messages. 8 Select if you want to check for new messages in all folders. 9 Select if you want to apply filters to new messages in the Inbox on the server.
  • Page 350 350 GroupWise 8 Interoperability Guide...

  • Page 351: Part Viii Mobile Devices

    VIII Mobile Devices V I I I ® If you own a mobile device, you can synchronize it with GroupWise . GroupWise has provided GroupWise Mobile Server for synchronizing several of the most common device. In addition, GroupWise has teamed up with BlackBerry for synchronizing of BlackBerry devices. Chapter 45, “GroupWise Mobile Server, Powered by Intellisync,”...
  • Page 352 352 GroupWise 8 Interoperability Guide...

  • Page 353: Groupwise Mobile Server, Powered By Intellisync

    E-mail Accelerator (excluding POP3, IMAP, Exchange Connector, Lotus Notes Connector, Workgroup, and PC Monitor) GroupWise Connector Mobile device synchronization For additional information documentation about GroupWise Mobile Server, visit the GroupWise Mobile Server 2 documentation Web site (http://www.novell.com/documentation/ groupwise_mobile_2/index.html). GroupWise Mobile Server, Powered by Intellisync...
  • Page 354 354 GroupWise 8 Interoperability Guide...

  • Page 355: Blackberry Enterprise Server

    Solution. It is designed to provide IT departments with simplified management and centralized control of wireless devices in a secure, scalable and flexible architecture. BlackBerry Enterprise Server v.4.1 for Novell GroupWise includes several new features to enhance end user productivity and back-end administration. These features include Novell GroupWise Messenger support, enhanced support for PowerPoint and Web Doc attachments, group- and role-based administration, localized data pass-through and SMS/PIN/call log auditing.
  • Page 356 356 GroupWise 8 Interoperability Guide...

  • Page 357: Part Ix Documentation Updates

    Documentation Updates This section lists updates to the GroupWise 8 Interoperability Guide that have been made since the ® initial release of GroupWise 8. The information helps 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 8 Interoperability Guide was republished.
  • Page 358 358 GroupWise 8 Interoperability Guide...

  • Page 359: A August 31, 2009 (Groupwise 8 Sp1)

    GroupWise System in a Linux File Systems (TSAFSGW) on Linux. Cluster,” on page 215 Novell Teaming and Conferencing Chapter 23, “Using GroupWise Updated for use with Novell Teaming 2.0. with Novell Teaming,” on page 239 Microsoft Clustering Services on Windows Section 33.5, “Planning Explained that multiple Internet Agents or multiple WebAccess Agents GroupWise Resource Groups,”...
  • Page 360 360 GroupWise 8 Interoperability Guide...

This manual is also suitable for:

Groupwise 8

Table of Contents