Novell GROUPWISE 7 - INTEROPERABILITY GUIDE, Manual

Share

Page: 356 / 485

Novell GROUPWISE 7 - INTEROPERABILITY GUIDE Manual Download Page 356

356

GroupWise 7 Interoperability Guide

n

ov

do

cx (e

n)

11
Ju

ly 20

08

34.4 Testing the WebAccess Agent in a

Heartbeat Cluster

After you have installed and configured the WebAccess Agent in your Heartbeat cluster, and the
WebAccess Application with your Web server, you can use the following methods to test whether
the WebAccess Agent fails over as expected:

In the

HA Management Client

, select a node where the WebAccess Agent is running, then click

Make the Node Standby

. The WebAccess Agent should fail over to another node and start

running again. This can also be done from the command line using the

crm_standby utility

(http://www.linux-ha.org/v2/AdminTools/crm_standby)

.

Using the

crm_resource utility (http://www.linux-ha.org/v2/AdminTools/crm_resource)

,

manually migrate a node where the WebAccess Agent is running.

If you receive the error

Unmanaged on node

, see

Step 7

in

“Testing Your WebAccess Agent

Installation on Each Node” on page 353

for troubleshooting assistance.

If you have set up your Heartbeat cluster in a test situation first, you can also use the following
methods for testing WebAccess Agent failover:

Power off the node where the WebAccess Agent is running. The WebAccess Agent should fail
over to another node and start running again.

Simulate the WebAccess Agent stopping unexpectedly (

kill -9

agent_PID

). If you have

configured the WebAccess Agent for automatic restart, as described in

“Enabling Automatic

GroupWise Agent Restart” on page 316

, the agent should start running again on the same node.

WARNING:

These last two tests should not be performed on a production system because they can

result in damage to GroupWise databases.

34.5 Managing the WebAccess Agent in a

Heartbeat Cluster

After you have installed the WebAccess Agent in a cluster, you should consider some long-term
management issues.

Section 34.5.1, “Updating GroupWise Objects with Cluster-Specific Descriptions,” on
page 357

Section 34.5.2, “Knowing What to Expect in a WebAccess Agent Failover Situation,” on
page 357

«
...
354
355
356
357
358
...
»

Summary of Contents for GROUPWISE 7 - INTEROPERABILITY GUIDE

Page 1: ...Novell www novell com novdocx en 11 July 2008 AUTHORIZED DOCUMENTATION GroupWise 7 Interoperability Guide GroupWise 7 June 25 2008 Interoperability Guide...

Page 2: ...export to entities on the current U S export exclusion lists or to any embargoed or terrorist countries as specified in the U S export laws You agree to not use deliverables for prohibited nuclear mis...

Page 3: ...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 prope...

Page 4: ...novdocx en 11 July 2008...

Page 5: ...37 2 9 1 System Clustering Worksheet 37 2 9 2 IP Address Worksheet 40 2 9 3 Agent Clustering Worksheet 41 3 Setting Up a Domain and Post Office in a NetWare Cluster 43 3 1 Preparing the Cluster for G...

Page 6: ...2 Knowing What to Expect in an Internet Agent Failover Situation 84 4 4 Internet Agent Clustering Worksheet 84 4 5 Internet Agent Quick Checklist 86 5 Implementing WebAccess in a NetWare Cluster 89 5...

Page 7: ...to GroupWise 7 and Novell Cluster Services on Linux 131 13 Planning GroupWise in a Linux Cluster 133 13 1 Installing Novell Cluster Services on Linux 134 13 2 Planning a Clustered Software Distributio...

Page 8: ...for the Internet Agent Domain 171 15 2 3 Installing and Configuring the Internet Agent in a Cluster 171 15 3 Testing the Internet Agent in a Linux Cluster 182 15 4 Managing the Internet Agent in a Lin...

Page 9: ...se System in a Linux Cluster 221 19 Updating a GroupWise System in a Linux Cluster 223 20 Moving an Existing Linux GroupWise 7 System into a Linux Cluster 225 21 Moving a Clustered GroupWise 7 System...

Page 10: ...e as the Conferencing E Mail System 263 24 1 1 Preparing for GroupWise Integration with Conferencing 263 24 1 2 Integrating GroupWise with Novell Conferencing 263 24 1 3 Testing GroupWise as the Novel...

Page 11: ...irectory for a Cluster 288 30 3 Planning a New Clustered Domain 288 30 4 Planning a New Clustered Post Office 289 30 5 Planning a New Library for a Clustered Post Office 290 30 6 Considering How to In...

Page 12: ...ternet Agent 327 33 1 6 Preparing Your Firewall for the Clustered Internet Agent 327 33 1 7 Planning the MTA Installation 328 33 1 8 Planning the Internet Agent Installation 328 33 2 Setting Up the In...

Page 13: ...2 1 Setting Up Native Heartbeat Resources for the Messenger Agents 371 39 2 2 Creating Your Messenger System and Installing the Messenger Agents 372 39 2 3 Changing Messenger Paths to Locations on th...

Page 14: ...5 Deciding Where to Install the Internet Agent and Its MTA 415 43 1 6 Planning the MTA Installation 416 43 1 7 Planning the Internet Agent Installation 416 43 2 Setting Up the Internet Agent in a Clu...

Page 15: ...senger in a Microsoft Cluster 443 49 1 Planning Your Messenger System in a Cluster 443 49 1 1 Understanding Your Cluster 443 49 1 2 Planning Messenger Administration 443 49 1 3 Deciding Where to Insta...

Page 16: ...2008 Part IX Documentation Updates 467 A June 25 2008 469 B March 14 2008 GroupWise 7 SP3 471 C October 24 2007 473 D April 16 2007 GroupWise 7 SP 2 475 E September 29 2006 477 F August 2 2006 479 G...

Page 17: ...feedback html and enter your comments there Documentation Updates For the most recent version of the GroupWise 7 Interoperability Guide visit the Novell GroupWise 7 documentation Web site http www no...

Page 18: ...can be written with a backslash for some platforms or a forward slash for other platforms the pathname is presented with a backslash Users of platforms that require a forward slash such as Linux shoul...

Page 19: ...Internet Agent in a NetWare Cluster on page 69 Chapter 5 Implementing WebAccess in a NetWare Cluster on page 89 Chapter 6 Implementing GroupWise Gateways in a Novell Cluster on page 107 Chapter 7 Mon...

Page 20: ...20 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 21: ...rage locations and applications can transfer from one server to another without interrupting their availability to users node A clustered server in other words a single NetWare server that is part of...

Page 22: ...r path for the volume Cluster enabling is highly recommended for GroupWise GroupWise volume As used in this section a cluster enabled shared volume that is used for GroupWise such as for storing a dom...

Page 23: ...ring the planning process component configuration alternatives are explained For example you might want the domain and post office together on the same shared volume or on different shared volumes You...

Page 24: ...cluster in Novell eDirectoryTM Adding nodes to the cluster Installing the Novell Cluster Services software on all nodes in the cluster Mounting the shared volumes where you will set up GroupWise domai...

Page 25: ...their MTAs are critical to GroupWise administrators although administrators might be more tolerant of a down server than end users are Critical domains in your system would be the primary domain and...

Page 26: ...anned on the Basic GroupWise System Worksheet To plan additional new post offices review Planning a New Post Office then print and fill out the Post Office Worksheet in Post Offices in the GroupWise 7...

Page 27: ...tion of clustering documentation for your version of NetWare as listed in Chapter 1 Introduction to GroupWise 7 and Novell Cluster Services on NetWare on page 21 The advantages of cluster enabling Gro...

Page 28: ...lumename_SERVER clustername default object name A new Volume Resource object stores property information for the cluster enabled volume such as start failover and failback mode information and load un...

Page 29: ...ces you must ensure that short name resolution is always successful For example in ConsoleOne if you right click a Domain object in the GroupWise View and then click Connect ConsoleOne must be able to...

Page 30: ...ace all of your virtual servers into DNS 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...

Page 31: ...sten on all IP addresses both primary and secondary that are bound to the server on their specified port numbers This means that any time there is a possibility of two of the same type of agent loadin...

Page 32: ...example port numbers 1677 and 1678 are both POA client server ports and port numbers 7180 through 7184 are all HTTP ports Incrementing from the default port numbers generates unique though related po...

Page 33: ...nother very large post office and heavily loaded POA reside If they did users on both post offices would notice a decrease in responsiveness of the GroupWise client SYSTEM CLUSTERING WORKSHEET If you...

Page 34: ...ystem directory on each GroupWise volume has several advantages If you change information in the agent startup files you only need to change it in one place not on every node on any GroupWise volume f...

Page 35: ...agent software Accidently installing a GroupWise Support Pack to the default location of sys system would not have the desired results if the original agent software was installed to the vol system d...

Page 36: ...penalty Make sure your nodes have sufficient memory to handle the number of memory spaces that might reside on them Keep in mind that if you load the MTA and the POA in different memory spaces the ag...

Page 37: ...Clustering Worksheet GROUPWISE AGENT INSTALLATION WORKSHEET Under Item 2 Agents and Locations mark POA Local to Post Office and MTA Local to Domain In a clustering environment a domain or post office...

Page 38: ...2 2 Installing Novell Cluster Services on page 24 5 Nodes in Cluster List the nodes that are part of the cluster that you set up for your GroupWise system For more information see Section 2 2 Installi...

Page 39: ...he cluster enabled volume is tied For more information see Section 2 4 Planning a New Clustered Post Office on page 26 and Section 2 6 Deciding Whether to Cluster Enable the Shared Volumes Used by Gro...

Page 40: ...e Area Access POA user startup switch setting POA password startup switch setting If you need a library for a clustered post office mark where you want to create its document storage area and provide...

Page 41: ...omain Name Domain Location Transfer this information from the System Clustering Worksheet item 10 3 Domain Failover Path List other nodes in the cluster where the GroupWise domain and its MTA could fa...

Page 42: ...que Port Numbers for Agents in the Cluster on page 31 8 Load Agents in Protected Memory No Yes MTA protected address space POA protected address space POA user startup switch setting POA password star...

Page 43: ...ection 3 8 What s Next on page 64 Section 3 9 Clustering Quick Checklists on page 65 3 1 Preparing the Cluster for GroupWise After you have installed Novell Cluster ServicesTM as described in Novell C...

Page 44: ...e Resolution To ensure that GroupWise volumes are always locatable configure the short name resolution methods that you want to rely on for GroupWise System Clustering Worksheet item 9 eDirectory on p...

Page 45: ...R gwcluster com gwcluster_gwvol1_SERVER When specifying the lines in the hosts files use System Clustering Worksheet item 7 or 8 for each IP_address and volume where a domain or post office resides Us...

Page 46: ...R ip_address cvsbind del cluster_volume_SERVER ip_address Remember that cluster_volume_SERVER represents the name of the virtual server created when you cluster enabled the volume Example cvsbind add...

Page 47: ...ng cluster specific details When you specify the ConsoleOne directory and the software distribution directory be sure to browse to each location through the GroupWise volume accessed in Step 1 above W...

Page 48: ...ration Guide 5 Create the new domain following the steps provided in Creating the New Domain in Domains in the GroupWise 7 Administration Guide Keep in mind the following cluster specific details Use...

Page 49: ...et item 7 map a drive to the GroupWise volume for the domain System Clustering Worksheet item 7 or Map a drive to the GroupWise volume for the post office System Clustering Worksheet item 8 The GroupW...

Page 50: ...ake sure you are still connected to the domain that owns the new post office 9 Rebuild the post office database for the new post office following the steps provided in Rebuilding Domain or Post Office...

Page 51: ...on on page 44 2 If you selected vol system on GroupWise volume as the agent installation location under Agent Clustering Worksheet item 1 create the vol system directory on the GroupWise volume access...

Page 52: ...rogram also adds a cluster startup switch to POA startup files to ensure that GroupWise clients detect the clustering environment and try more persistently to reconnect in a failover failback or migra...

Page 53: ...to display the default volume resource load script for the GroupWise volume 3 Make the following changes to the default load script Remove the trustmig command It is not necessary to migrate trustees...

Page 54: ...start name The result would look similar to the following example NOTE The set commands are needed in the load script only when the agents are not running in protected memory The address space paramet...

Page 55: ...pletely unloaded resulting in the agents hanging in the unloading state load the delay nlm program and set a delay of several seconds before issuing the unload kill address space command to allow the...

Page 56: ...Volume Resource object volume_SERVER click Nodes to display the default failover path for the GroupWise volume resource 2 Arrange the nodes in the cluster into the desired failover path for the domain...

Page 57: ...ume To create a new startup file without installing the agent software 1 Make a copy of an existing startup file and name it after the domain or post office that will be serviced by the agent 2 Edit t...

Page 58: ...he GroupWise volume 3 Following the pattern of the existing load commands add load commands for the new instances of the agents you are setting up Use Ctrl C to copy and Ctrl V to paste lines in the l...

Page 59: ...e with these tasks see Section 3 6 Testing Your Clustered GroupWise System on page 59 3 6 Testing Your Clustered GroupWise System After you have configured the GroupWise volume resources you can test...

Page 60: ...tions After setting up 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...

Page 61: ...rrently running on 7 Click OK to save the POA description 8 If necessary continue with Recording Cluster Specific Information for a Software Distribution Directory on page 61 or Skip to Knowing What t...

Page 62: ...page 63 Configuring Your GroupWise Cluster On the main Novell Remote Manager page 1 In the left frame scroll down to the Clustering section then click Cluster Config The Cluster Configuration page dis...

Page 63: ...form the specified action 5 On the Cluster Configuration page click New Cluster Volume to create a new GroupWise Volume Resource object then follow the instructions to provide the information needed t...

Page 64: ...of sending a message when the POA went down Notify can continue running even if the connection to the POA becomes unavailable and then it reconnects automatically when the POA is again available The...

Page 65: ...ere GroupWise domains and post offices will reside See Section 3 1 2 Cluster Enabling Shared Volumes for Use with GroupWise on page 43 Make sure that short name resolution works throughout your networ...

Page 66: ...er Enabling Shared Volumes for Use with GroupWise on page 43 Make sure that short name resolution for the new domain volume works throughout your network See Section 3 1 3 Configuring Short Name Resol...

Page 67: ...ution for the new post office volume works throughout your network See Section 3 1 3 Configuring Short Name Resolution on page 44 Create the new post office See Section 3 4 Creating a New Post Office...

Page 68: ...and See Modifying the Volume Resource Unload Script for the Agents on page 54 Set up the post office volume failover path and policies See Setting the Failover Path and Policies for the Agents on page...

Page 69: ...rnet Agent in a Cluster A main 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 separ...

Page 70: ...cluster enabling volumes see Section 2 6 Deciding Whether to Cluster Enable the Shared Volumes Used by GroupWise on page 27 which describes the issues in the context of planning MTA and POA installati...

Page 71: ...1 Standard Ports 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...

Page 72: ...th several servers in its failover path it is an easy choice Install it once to a vol system directory on the Internet Agent volume 4 1 7 Deciding Whether to Run the Internet Agent and Its MTA in Prot...

Page 73: ...et Agent in a Cluster on page 73 4 2 Setting Up the Internet Agent in a Cluster You should already have reviewed Section 4 1 Planning the Internet Agent in a Cluster on page 69 and filled out the Sect...

Page 74: ...ntinue with Installing the MTA for the Internet Agent Domain 4 2 3 Installing the MTA for the Internet Agent Domain The MTA for the Internet Agent domain can be installed just like any other MTA in yo...

Page 75: ...formation later when you create the load script for the Volume Resource object 4 If you need to install the Internet Agent to sys system to each node in the cluster 4a Repeat Step 3 mapping new drives...

Page 76: ...ering Worksheet items 4 and 6 add a search add command to add the new vol system directory to the server search path search add volume system If you selected sys system on each node as the installatio...

Page 77: ...ame volume system gwia nlm gwia cfg protection restart addr_space_name The result would look similar to the following example NOTE The set commands are needed in the load script only when the MTA and...

Page 78: ...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 is...

Page 79: ...Path and Policies for the Internet Agent To modify the failover path and policies for the Internet Agent volume resource 1 In ConsoleOne in the properties pages for the Volume Resource object volume_...

Page 80: ...r 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 i...

Page 81: ...object not the name of a physical server in the cluster 3 Make changes if necessary 4 Continue with Verifying Post Office Links Verifying Post Office Links In the Internet Agent object properties page...

Page 82: ...mn for the volume resource now displays Running 3 Observe the server console where the Internet Agent and its MTA are loading to see that they start and run correctly If you are using protected memory...

Page 83: ...configuration of your system changes Recording Cluster Specific Information about the Internet Agent Domain and Its MTA on page 83 Recording Cluster Specific Information about the Internet Agent on p...

Page 84: ...not attempt to reconnect automatically so the user must exit the client and restart it to reestablish the connection after the failover process is complete Fortunately the Internet Agent restarts quic...

Page 85: ...rnet Agent and Its MTA on page 71 6 Internet Agent Installation Location vol system on the Internet Agent volume sys system on each node Consolidate multiple Internet Agent configuration files on Inte...

Page 86: ...the search add command optional If you will not run the MTA and the Internet Agent in protected memory add the set auto restart commands and the set developer option off command Add the load commands...

Page 87: ...red Internet Agent See Section 4 2 5 Testing the Clustered Internet Agent on page 82 Record cluster specific information in the properties pages of the GroupWise objects associated with the Internet A...

Page 88: ...88 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 89: ...oupWise WebAccess Overview in Installing GroupWise WebAccess in the GroupWise 7 Installation Guide As you plan WebAccess in a clustering environment you must keep in mind that WebAccess consists of tw...

Page 90: ...location for the domain directory on the Domain Worksheet include the shared volume where you want the domain directory to reside Do not concern yourself with the GroupWise agent information on the D...

Page 91: ...heet for your system print it now and fill in current system information 5 2 5 Deciding Where to Install the WebAccess Agent and Its MTA As with the MTA and the POA you can choose to install the WebAc...

Page 92: ...use when you install the MTA IMPORTANT Do not install the NetWare MTA until you are instructed to do so in Section 5 3 Setting Up WebAccess in a Cluster on page 93 5 2 8 Planning the WebAccess Instal...

Page 93: ...with the WebAccess Agent on page 93 Section 5 3 2 Creating a Domain for the WebAccess Agent on page 94 Section 5 3 3 Installing the MTA for the WebAccess Agent Domain on page 94 Section 5 3 4 Install...

Page 94: ...follow the instructions in Section 3 3 Creating a New Secondary Domain in a Cluster on page 48 taking your information from the WebAccess Clustering Worksheet rather than the System Clustering Workshe...

Page 95: ...GroupWise WebAccess Agent Do not install the WebAccess Application at this time Use items 2 through 12 on the GroupWise WebAccess Installation Worksheet that you filled out in Planning the WebAccess I...

Page 96: ...script If other GroupWise agents are already running from this volume some of the modifications have already been made 3 Make the following changes to the default load script Remove the trustmig comm...

Page 97: ...e located in the vol system directory into the load script Use Ctrl C and Ctrl V to copy and paste text into the load script page load volume system gwinter nlm ph volume domain wpgate webac70a user u...

Page 98: ...e agents are already running from this volume some of the modifications have already been made 2 Make the following changes to the default unload script If you marked Yes under Load WebAccess Agent an...

Page 99: ...ing the Failover Path and Policies for the WebAccess Agent Setting the Failover Path and Policies for the WebAccess Agent To modify the failover path and policies for the WebAccess Agent volume resour...

Page 100: ...server you must install the WebAccess Application on each node where the Web server is installed as described in Installing the WebAccess Application and WebPublisher Application in Installing GroupW...

Page 101: ...cific Information about the WebAccess Agent Domain and Its MTA To permanently record important cluster specific information for the WebAccess Agent domain 1 In ConsoleOne browse to and right click the...

Page 102: ...tes to a different node the cached credentials are lost Consequently the user needs to restart the WebAccess client in order to re authenticate and re establish the credentials If the WebAccess Agent...

Page 103: ...ing a New Domain for the WebAccess Agent on page 90 3 WebAccess Agent Failover Path List other nodes in the cluster where the WebAccess Agent and its MTA could fail over For more information see Deter...

Page 104: ...n the MTA and the WebAccess Agent in protected memory add the set auto restart commands and the set developer option off command Add the load commands for the MTA and the WebAccess Agent separating th...

Page 105: ...ifying the Volume Resource Unload Script for the WebAccess Agent on page 98 Set up the WebAccess Agent volume failover path and policies See Setting the Failover Path and Policies for the WebAccess Ag...

Page 106: ...106 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 107: ...e gateway The gateway domain should be created on a cluster enabled volume This enables the gateway to fail over independently from other GroupWise components If you have set up the Internet Agent or...

Page 108: ...108 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 109: ...the IP address associated with the cluster enabled volume where the agent s domain or post office resides When an agent fails over or migrates to a different node its status in Monitor displays as Not...

Page 110: ...110 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 111: ...node and if that node attempted to start an instance of GWTSA for each GroupWise volume only the first instance would run successfully Subsequent instances of GWTSA would fail and the domains and pos...

Page 112: ...server in your NetWare cluster Then you can use the home switch to specify shared volumes and paths rather than physical volumes and paths For example vserver clustername_volumename_SERVER home volume...

Page 113: ...to reconnect to the next node When the next node is fully up and responding the backup recommences starting with the resource that was being backed up when the disruption occurred To restore data in a...

Page 114: ...114 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 115: ...update all nodes on the failover path of each domain and post office at once because each domain and post office should be serviced by only one version of the agent software If you do not update all n...

Page 116: ...116 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 117: ...ices Decide which nodes in your storage area network you will have on failover paths for the GroupWise agents Review Chapter 2 Planning GroupWise in a NetWare Cluster on page 23 Fill out the System Cl...

Page 118: ...ost Office on page 27 Move GroupWise administration into the cluster as needed Add other components to your clustered GroupWise system as needed following the instructions in Chapter 4 Implementing th...

Page 119: ...the information you need as you set up the Messenger agents in a clustering environment You should print the worksheet and fill it out as you complete the tasks listed below Understanding Your Cluste...

Page 120: ...der 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 IMPORTANT Cluster enabling relies on su...

Page 121: ...lume Determining an Appropriate Failover Path for the Messenger Volume By default a Messenger volume is configured to have all nodes in the cluster in its failover path organized in ascending alphanum...

Page 122: ...ring on the Messenger System Worksheet mark 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 t...

Page 123: ...ger system on a Messenger volume Preparing the Cluster for Messenger on page 123 Running the Messenger Installation Program on page 123 Configuring the Messenger Volume Resource to Load and Unload the...

Page 124: ...cluster how the Messenger agents are loaded and unloaded and how failover and failback situations are handled 1 In ConsoleOne browse to and select the Cluster object If necessary click View Console V...

Page 125: ...ts From the node where the Messenger volume was mounted during installation copy the following files to the cluster volume Table 11 2 LDAP and QuickFinder Files to Copy If you are running in a languag...

Page 126: ...e loading to see that they start and run correctly 4 Click the new Messenger volume resource then click Offline The State column for the volume resource returns to Offline 5 Observe the server console...

Page 127: ...me Cluster IP Address Record the name of the name of the NetWare Cluster object where your Messenger system will be located Also record the virtual IP address of the cluster that will remain constant...

Page 128: ...or Messenger Agents Cluster volume IP address If you plan to install the Messenger agents on a shared volume specify the name cluster_volume of the shared volume Specify the IP address of the virtual...

Page 129: ...ternet Agent in a Linux Cluster on page 167 Chapter 16 Implementing WebAccess in a Linux Cluster on page 187 Chapter 17 Implementing GroupWise Monitor in a Linux Cluster on page 207 Chapter 18 Backing...

Page 130: ...130 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 131: ...nux traditional file system disk partitions shared NSS volumes Novell Storage ServicesTM volumes and shared pools virtual servers NOTE For simplicity this section uses the term shared partition to rep...

Page 132: ...from a single failed node fail over to several different nodes in order to distribute the load from the failed node across multiple nodes For example if a node runs a cluster resource consisting of a...

Page 133: ...plan the following GroupWise components in a cluster A new GroupWise system consisting of the primary domain and the initial post office A new secondary domain A new post office The GroupWise agents...

Page 134: ...in Installation and Setup in the OES Novell Cluster Services 1 8 2 Administration Guide for Linux IMPORTANT Cluster enabling is required for GroupWise Mounting the shared partitions where you want to...

Page 135: ...t is a vital partner with the GroupWise High Availability service described in Enabling the High Availability Service for the Linux GroupWise Agents in Installing GroupWise Agents in the GroupWise 7 I...

Page 136: ...the node where you will be running the GroupWise Installation program Do not concern yourself with the GroupWise agent information on the worksheet You will plan the agent installation later If you a...

Page 137: ...However in a Linux cluster you should not plan to locate a document storage area on a remote storage area If you choose to place it outside the post office directory structure it should still be loca...

Page 138: ...nformation see Simplifying Client Server Access with a GroupWise Name Server in Post Office Agent in the GroupWise 7 Administration Guide 13 6 2 Determining Appropriate Failover Lists for the Agents B...

Page 139: ...tallation Guide for each location where you will install the Linux MTA and or POA IMPORTANT Do not install the Linux agent software until you are instructed to do so in Chapter 14 Setting Up a Domain...

Page 140: ...that you set up for your GroupWise system Also list the file system type reiserfs ext3 etc device name sda2 hda1 etc and mount point directory mnt mail etc for each You need this information as you cr...

Page 141: ...ce mark where you want to create its document storage area and provide a directory if necessary For more information see Section 13 5 Planning a New Library for a Clustered Post Office on page 137 Ite...

Page 142: ...ffice secondary IP address in the cluster See Section 13 6 1 Recording Secondary IP Addresses for the Agents on page 138 7 Cluster Resource Information Path to the cluster resource mount point IP addr...

Page 143: ...might be creating your primary domain and initial post office on the same GroupWise partition or on two different partitions After you have created the primary domain and initial post office and then...

Page 144: ...n the Preferred Node on page 147 14 2 Creating a New Secondary Domain in a Linux Cluster After you have set up the primary domain and initial post office as described in Section 14 1 Setting Up a New...

Page 145: ...nistration Guide 4 Create the new post office following the steps provided in Creating the New Post Office in Post Offices in the GroupWise 7 Administration Guide Use the Post Office Worksheet you fil...

Page 146: ...oupWise system You are now ready to install and configure the agents on additional nodes and set up the agent software for use in your cluster Section 14 4 1 Installing and Setting Up the Agents in Yo...

Page 147: ...out in Section 13 6 Deciding How to Install and Configure the Linux Agents in a Cluster on page 138 paying special attention to the cluster resource information on the Domains Post Offices page As a r...

Page 148: ...lly whenever a node restarts 5 Configure the agents to run as a non root user as described in the applicable section of the GroupWise 7 Installation Guide Running the Linux GroupWise Agents as a Non r...

Page 149: ...f file 5 Select the GroupWise agents that you want to configure on the current cluster node then click OK The Import Clustering Data option performs the following configuration actions for each subseq...

Page 150: ...e agents bin gwpoa show post_office poa 2 Stop the agents by clicking File Exit 3 After you can see that the agents start successfully test them by starting them as daemons as described in Starting th...

Page 151: ...nce obtaining these files see Server Certificates and SSL Encryption in Security Administration in the GroupWise 7 Administration Guide 3 In ConsoleOne browse to and select the Domain object 4 Right c...

Page 152: ...the post office Complete the following tasks for each cluster resource Modifying the Cluster Resource Load Script for the Agents on page 152 Modifying the Cluster Resource Unload Script for the Agent...

Page 153: ...ing changes to set up the load script for the agents 5a As needed in the mount command change reiserfs to whatever file system type is in use on nodes in the cluster System Clustering Worksheet item 5...

Page 154: ...d grpwise start post_office domain The result would be similar to the following 6 If this is a traditional Linux volume use the following load script bin bash opt novell ncs lib ncsfunc define the IP...

Page 155: ...a domain on the partition use the following command to start the MTA etc init d grpwise start domain 6f If you created a post office on the partition use the following command to start the POA etc ini...

Page 156: ...ust the sleep command as needed so that the agents can shut down normally on your system without being inadvertently killed by the kill service command 2c In the kill service command used if the agent...

Page 157: ...etc init d grpwise stop post_office domain 3c On the RESOURCE_IP line change 172 16 5 18 to the secondary IP address used in the load script 3d On the MOUNT_POINT line change mnt mount_point to the mo...

Page 158: ...in the cluster into the desired failover list for the domain or post office under Agent Clustering Worksheet items 3 or 6 3 Click OK 14 4 4 Setting Up New Instances of the Agents without Installing t...

Page 159: ...u created the new domain and or post office on a new GroupWise partition skip back to Section 14 4 3 Configuring GroupWise Cluster Resources to Load and Unload the Agents on page 152 for instructions...

Page 160: ...unload scripts If you need assistance with these tasks see Testing Your Clustered GroupWise System 14 5 Testing Your Clustered GroupWise System After you have configured the GroupWise cluster resourc...

Page 161: ...owing What to Expect in MTA and POA Failover Situations on page 163 14 6 1 Updating GroupWise Objects with Cluster Specific Descriptions After setting up your clustered GroupWise system while the clus...

Page 162: ...click Properties 2 In the Description field of the post office Identification page provide a cluster specific description of the post office including the secondary IP address of its GroupWise partit...

Page 163: ...s of sending a message when the POA went down Notify can continue running even if the connection to the POA becomes unavailable and then it reconnects automatically when the POA is again available The...

Page 164: ...nitial post office See Section 14 4 Installing and Configuring the MTA and the POA in a Cluster on page 146 Modify the cluster resource load scripts See Modifying the Cluster Resource Load Script for...

Page 165: ...nning a New Clustered Post Office on page 137 and Section 13 5 Planning a New Library for a Clustered Post Office on page 137 Create the new post office See Section 14 3 Creating a New Post Office in...

Page 166: ...166 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 167: ...Section 15 6 Internet Agent Quick Checklist on page 185 15 1 Planning the Internet Agent in a Linux Cluster A major system configuration difference between the Internet Agent in a clustering environm...

Page 168: ...5 2 1 Creating a Domain for the Internet Agent on page 171 15 1 2 Selecting the Internet Agent Partition and Secondary IP Address As with the MTA and the POA the Internet Agent needs a secondary IP ad...

Page 169: ...ition 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 When using...

Page 170: ...r installing the Internet Agent configure your firewall as needed to handle the Internet Agent s use of primary and secondary IP addresses when sending and receiving messages 15 1 7 Planning the MTA I...

Page 171: ...After you have created the domain continue with Installing the MTA for the Internet Agent Domain 15 2 2 Installing the MTA for the Internet Agent Domain The MTA for the Internet Agent domain can be in...

Page 172: ...ou created in Step 6 in Section 14 1 Setting Up a New GroupWise System in a Linux Cluster on page 143 2 Mount the Internet Agent partition Internet Agent Clustering Worksheet item 1 where the Internet...

Page 173: ...ated in the etc opt novell groupwise directory If another GroupWise agent has already been installed on this cluster node the gwha conf file is updated to include the Internet Agent The clusterimport...

Page 174: ...tallation program page 3 Install the Internet Agent software on the cluster node as usual but do not use the Configure option 4 On the main page of the Installation program click Import Clustering Dat...

Page 175: ...the Internet Agent to fail over to it 8 Continue with Testing Your Internet Agent Installation on Each Node Testing Your Internet Agent Installation on Each Node 1 Test the Internet Agent by starting...

Page 176: ...certificate file 7 In the SSL Key File field browse to and select the key file 8 Click OK 9 Continue with Configuring the Internet Agent Cluster Resource to Load and Unload the Internet Agent and Its...

Page 177: ...in the cluster 5c In the mount command change mnt generic to the mount point directory in use on nodes in the cluster 5d In the add_secondary_ipaddress command change a b c d to the secondary IP addre...

Page 178: ...init d grpwise start domain 6f Use the following commands to start the Internet Agent and its MTA etc init d grpwise start domain etc init d grpwise start domain gwia 7 Click OK to save the load scrip...

Page 179: ...irectory used in the load script 2e In the del_secondary_ipaddress command change a b c d to the secondary IP address used in the load script 2f In the umount command change mnt generic to the mount p...

Page 180: ...des 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 In...

Page 181: ...ctories match the mount point directory and the domain directory 3 Make changes if necessary 4 Continue with Verifying Post Office Links Verifying Post Office Links In the Internet Agent object proper...

Page 182: ...then click Cluster Manager 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 y...

Page 183: ...ster 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 in the GroupWise objects if the configuration of you...

Page 184: ...clients POP3 IMAP4 and LDAP receive an error message that the node is not available Most of the clients do not attempt to reconnect automatically so the user must exit the client and restart it to ree...

Page 185: ...Cluster Resource Load Script for the Internet Agent and Its MTA on page 176 Modify the Internet Agent cluster resource unload script See Modifying the Cluster Resource Unload Script for the Internet...

Page 186: ...g for Your Clustered GroupWise System on page 180 Double check the cluster specific Internet Agent object properties See Verifying Internet Agent Object Properties on page 180 Test the clustered Inter...

Page 187: ...nux Cluster on page 202 Section 16 6 WebAccess Agent Clustering Worksheet on page 204 Section 16 7 WebAccess Agent Quick Checklist on page 205 16 1 Understanding the WebAccess Components If you are no...

Page 188: ...iew Planning a New Domain then print and fill out the Domain Worksheet in Domains in the GroupWise 7 Administration Guide Keep in mind the following cluster specific details When you specify the locat...

Page 189: ...r principle As with the MTA and the POA you need to decide which nodes in the cluster are appropriate locations for the WebAccess Agent partition to fail over to You must install the WebAccess Agent s...

Page 190: ...WebAccess Agent software until you are instructed to do so in Setting Up the WebAccess Agent in a Linux Cluster 16 2 7 Planning the WebAccess Application Installation The WebAccess Application must be...

Page 191: ...nd Configuring the WebAccess Agent in a Cluster 16 3 3 Installing and Configuring the WebAccess Agent in a Cluster After you have created a domain for the WebAccess Agent and installed the MTA for tha...

Page 192: ...uster resource information on the Server Information page As a result of selecting Configure GroupWise for Clustering on the preferred node the following cluster specific configuration actions are per...

Page 193: ...nt Installation Program on Subsequent Nodes 1 On the next node in the WebAccess Agent failover list mount the WebAccess Agent partition WebAccess Agent Clustering Worksheet item 1 where the WebAccess...

Page 194: ...d on the shared resource they do not need to be customized for each cluster node 6 Repeat Step 1 through Step 5 for each cluster node in the WebAccess Agent failover list After you install and configu...

Page 195: ...g the WebAccess Agent Cluster Resource to Load and Unload the WebAccess Agent and Its MTA on page 196 Configuring the Clustered WebAccess Agent for SSL If you plan to enable SSL as described in Securi...

Page 196: ...ter Resource Load Script for the WebAccess Agent and Its MTA The cluster resource load script executes whenever the WebAccess Agent cluster resource comes online To set up the load script in iManager...

Page 197: ...iserf 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...

Page 198: ...vell ncs lib ncsfuncs request service stop ignore_error etc init d myservice stop stop service otherwise sleep 8 ignore_error fuser k mnt generic del the IP address ignore_error del_secondary_ipaddres...

Page 199: ...lowing changes to set up the unload script for the agents 3a Use the following command to stop the WebAccess Agent etc init d grpwise stop domain webac70a 3b Use the following command to stop the MTA...

Page 200: ...urself with the configuration of a clustered WebAccess Agent Accessing WebAccess Agent Object Properties on page 200 Verifying Post Office Links on page 200 Forcing Use of the Web Access Agent Seconda...

Page 201: ...e WebAccess Application on each node where the Web server is installed as described in Installing the WebAccess Application and WebPublisher Application in Installing GroupWise WebAccess in the GroupW...

Page 202: ...e 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 7 Repeat Step 2 whenever you ar...

Page 203: ...cific description of the WebAccess Agent domain including the secondary IP address of its GroupWise partition 3 Click OK to save the WebAccess Agent domain description 4 Select the Internet Agent Doma...

Page 204: ...ing stops its threads and stops the Document Viewer Agent For a busy WebAccess Agent you might need to wait several minutes for it to shut down properly 16 6 WebAccess Agent Clustering Worksheet Item...

Page 205: ...t for the WebAccess Agent and Its MTA on page 198 Set up the WebAccess Agent failover list and policies See Setting the Failover List and Policies for the WebAccess Agent and Its MTA on page 199 Doubl...

Page 206: ...206 GroupWise 7 Interoperability Guide novdocx en 11 July 2008 See Section 16 5 1 Updating GroupWise Objects with Cluster Specific Descriptions on page 203...

Page 207: ...on page 218 Section 17 6 Monitor Agent Clustering Worksheet on page 218 Section 17 7 Monitor Agent Quick Checklist on page 219 17 1 Understanding the Monitor Components If you are not familiar with Gr...

Page 208: ...or Agent on page 209 Section 17 2 6 Planning the Monitor Agent Installation on page 210 17 2 1 Selecting a Domain for Access during Monitor Agent Installation During installation the Monitor Agent Ins...

Page 209: ...You must install the Monitor Agent software on all of the nodes where you want the Monitor Agent to be able to fail over For a review of failover lists see Section 13 6 2 Determining Appropriate Fail...

Page 210: ...figuring the Monitor Agent on Each Node in Your Cluster on page 210 Section 17 3 2 Configuring the Monitor Agent Cluster Resource to Load and Unload the Monitor Agent on page 213 17 3 1 Installing and...

Page 211: ...ter node it is running on The HOME_PATH option includes the mount point and the path to the database so that the configuration file is valid when mounted to each cluster node The log startup switch in...

Page 212: ...provide an SSL certificate file You can place the file on the Monitor Agent partition rather than each node 1 Create a directory on the Monitor Agent partition where you want to store the certificate...

Page 213: ...ick Cluster Options 2 In the Cluster field browse to the Cluster object where the Monitor Agent cluster resource is located 3 Click the Cluster object to display the cluster resources that belong to t...

Page 214: ...nt point MOUNT_POINT mnt mount_point mount the file system exit_on_error mount t MOUNT_FS MOUNT_DEV MOUNT_POINT add the IP address exit_on_error add_secondary_ipaddress RESOURCE_IP etc init d grpwise...

Page 215: ...make the following changes 2a In the stop service command change myservice stop to the command to stop the Monitor Agent etc init d grpwise ma stop 2b Adjust the sleep command as needed so that the Mo...

Page 216: ...fuser k command that follows 3e In the fuser k command used if the Monitor Agent does not stop normally change k to mk The m parameter obtains the PID numbers of the processes to kill 4 Click OK to s...

Page 217: ...ager expand Clusters then click Cluster Manager The new Monitor Agent cluster resource shows Offline in the State column 2 Click the new Monitor Agent cluster resource then click Online 3 Select the c...

Page 218: ...rtition for Domain Domain Name Domain Directory Specify a GroupWise partition where there is a domain database from which the Monitor Agent can gather information about agents to monitor Also provide...

Page 219: ...n 17 3 1 Installing and Configuring the Monitor Agent on Each Node in Your Cluster on page 210 Modify the Monitor Agent cluster resource load script See Modifying the Cluster Resource Load Script for...

Page 220: ...220 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 221: ...Cluster To back up GroupWise data in a Linux cluster 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...

Page 222: ...222 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 223: ...tant to update all nodes on the failover list of each domain and post office at the same time because each domain and post office should serviced by only one one version of the agent software If you d...

Page 224: ...224 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 225: ...ning GroupWise in a Linux Cluster on page 133 Fill out the Section 13 7 1 System Clustering Worksheet on page 140 to help you decide which domains and post offices you want move to which shared partit...

Page 226: ...GroupWise 7 Interoperability Guide novdocx en 11 July 2008 Chapter 17 Implementing GroupWise Monitor in a Linux Cluster on page 207 Chapter 18 Backing Up a GroupWise System in a Linux Cluster on page...

Page 227: ...e a domain and MTA on a NetWare server cannot fail over to a Linux server they must fail over to another NetWare server Ideally you should administer a GroupWise system on Linux using the Linux versio...

Page 228: ...228 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 229: ...our Messenger System in a Linux Cluster Because the Messenger agents are not associated with GroupWise domains or post offices the Messenger agents are easier to implement in a cluster than are the Gr...

Page 230: ...Messenger Agents A cluster resource is a shared partition secondary IP address application service Web server etc that can function successfully anywhere in the cluster Cluster resources include the G...

Page 231: ...s on page 235 22 2 1 Creating Your Messenger System and Installing the Messenger Agents The Messenger Installation program walks you through setting up your Messenger system and installing the Messeng...

Page 232: ...the probable configuration for the Messenger agents you are installing on the current node 6 Enter 1 for Proceed with these settings or Enter 2 for Change the settings then modify the configuration f...

Page 233: ...the Archive Agent Queue Path on page 234 Setting the Messaging Agent Log Path on page 234 Setting the Archive Agent Log Path on page 234 After settings these directories continue with Section 22 2 3 C...

Page 234: ...directory for the Archive 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 Messenge...

Page 235: ...odifying the Cluster Load Script for the Messenger Agents 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 t...

Page 236: ...nt MOUNT_POINT mnt mount_point mount the file system exit_on_error mount t MOUNT_FS MOUNT_DEV MOUNT_POINT add the IP address exit_on_error add_secondary_ipaddress RESOURCE_IP etc init d novell nmma st...

Page 237: ...is is an NSS volume or a shared pool make the following changes to the Messenger unload script 2a In the stop service command change myservice stop to the command to stop the Messenger agents etc init...

Page 238: ...IP address used in the load script 3d On the MOUNT_POINT line change mnt mount_point to the mount point directory used in the load script 3e Adjust the sleep command as needed so that the Messenger ag...

Page 239: ...into the desired failover list for the Messenger agents under Messenger Clustering Worksheet item 3 3 Click OK 22 3 Testing Your Clustered Messenger System After you have configured the Messenger clus...

Page 240: ...st Messenger clients reconnect automatically as soon as the Messaging Agent restarts on the next node Users who are actively carrying on conversations notice the interruption but do not need to do any...

Page 241: ...rtition to store its log files temporary files and queue directories Specify the name of the shared partition in the your cluster that the Messaging Agent can use for these purposes also specify the s...

Page 242: ...ys available not matter what node the Messenger agents are running on See Section 22 2 2 Changing Messenger Paths to Locations on the Messenger Partition on page 233 Modify the Messenger agents cluste...

Page 243: ...include specific instructions for integrating Novell Teaming or Conferencing with eDirectoryTM or GroupWise This section of the GroupWise 8 Interoperability Guide supplies these product specific inst...

Page 244: ...244 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 245: ...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 cr...

Page 246: ...server before you install Teaming IMPORTANT Make sure you download the JDK not the Java Runtime Environment JRE 1 Go to the following URL Java SE Downloads Previous Release http java sun com javase d...

Page 247: ...the MySQL root user to root which matches the default MySQL configuration in the Teaming installer The following are some basic and useful MySQL commands If you would like to administer MySQL using a...

Page 248: ...ve rights It is used as the administrative e mail address from which the Teaming site sends messages to GroupWise mailboxes It is also used to own the GroupWise resources associated with Teaming folde...

Page 249: ...tallation you set up outgoing E Mail in the Outbound E Mail Configuration window of the Teaming installer If you need to change the outbound e mail configuration after installation you need to use the...

Page 250: ...ions of changes in your Teaming site s content and messages from Teaming site users sent to GroupWise mailboxes Your Novell Teaming system needs an administrator e mail account that is responsible for...

Page 251: ...blogs files for sharing with the team calendar items and so on You should already have created at least one workspace by following the instructions in Create Your Initial Workspaces in Configuring No...

Page 252: ...post items to the Discussion folder they can mail a posting to an e mail address similar to salesdisc corporate net The message is delivered to the resource mailbox where it is picked up by the Teami...

Page 253: ...ted for use with Teaming then click OK 8 Click OK again to add the listed resources to the distribution list Setting Passwords for GroupWise Resources Because the Teaming administrator user owns all t...

Page 254: ...o this resource you can simply click Proxy resource_name 5 In the resource mailbox click Tools Options Security Use the same password for the resource mailbox that you used for the Teaming administrat...

Page 255: ...edule for this folder as well 6 Repeat Step 2 through Step 5 for each Teaming folder that you want GroupWise users to be able to post to by way of e mail 7 When you are finished adding resource e mail...

Page 256: ...t is located right click the Internet Agent object then click Properties 2 Click GroupWise POP3 IMAP4 3 Make sure that either POP or IMAP is enabled to match the configuration you provided in the Inbo...

Page 257: ...OK to save the settings 23 5 3 Testing GroupWise Integration with Novell Teaming After you have configured outgoing and incoming e mail you are ready to test your e mail integration Testing Outgoing E...

Page 258: ...embers of the team especially remote team members to verify that they also received the notification 9 Open the message then click the link to verify that it opens the page of the Teaming site from wh...

Page 259: ...ted on a Teaming calendar arrive just like appointments created on a GroupWise calendar When you open the Teaming appointment you can accept it or decline it If you accept it the Teaming appointment i...

Page 260: ...aming 1 Edit the liferay portlet xml file Each portlet is defined between portlet and portlet tags Each portlet has a name which is a number from 1 to113 2 To turn on a portlet edit the edit the value...

Page 261: ...ned categories include cms journal collaboration community entertainment category polls category religion category christianity category sample category shopping category wiki category workflow catego...

Page 262: ...tomcat 5 5 jdk5 4 3 0 webapps ROOT WEB INF classes content NOTE The part of the path before the webapps directory might be different on your system depending on where you installed Novell Teaming 8 Re...

Page 263: ...ail System on page 264 24 1 1 Preparing for GroupWise Integration with Conferencing Before you install Conferencing with GroupWise you need to gather the following GroupWise information A GroupWise us...

Page 264: ...er y n 7 If you want the Conferencing mailer to authenticate to the GroupWise Internet Agent type y then press Enter 7a Specify a valid GroupWise username then press Enter 7b Specify the password for...

Page 265: ...ve Teaming or Conferencing as well as iChain installed configured and running Section 25 1 1 Meeting iChain Requirements on page 265 Section 25 1 2 Setting Up an iChain Web Server Accelerator for Team...

Page 266: ...t field on the right specify the port number that the iChain proxy server should use to communicate with the Web server where Teaming or Conferencing is installed 7b If desired select Enable Secure Ac...

Page 267: ...AP server by the iChain OLAC process so that users can log in automatically 5d Click OK to save the OLAC parameters 6 When prompted click Yes to refresh the iChain proxy configuration with the new cha...

Page 268: ...268 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 269: ...IV 269 novdocx en 11 July 2008 IV Other Novell Products Chapter 26 GroupWise DirXML Driver for Novell Identity Manager on page 271 Chapter 27 GroupWise Customization Tools on page 275 Chapter 28 Nove...

Page 270: ...270 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 271: ...se administrative actions in ConsoleOne require that you stop the GroupWise DirXML driver or disable a user s association with it before you perform the action and usually restart the GroupWise DirXML...

Page 272: ...onvert External Entity to User in System in the GroupWise 7 Administration Guide 3 Using the DirXML Management role restart the GroupWise DirXML driver 26 1 4 Converting a User to an External Entity 1...

Page 273: ...river 2 Resolve the invalid association as described in Invalid Associations in System in the GroupWise 7 Administration Guide 26 1 8 Disabling the DirXML Warnings 1 In ConsoleOne deselect Display Dir...

Page 274: ...274 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 275: ...ject_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 For example you can modify the GroupWise client toolba...

Page 276: ...uires that objects support one or more interfaces or sets of functions For more information see GroupWise MAPI http developer novell com wiki index php GroupWise_MAPI GroupWise Events Provides event n...

Page 277: ...gured to use WebAccess you must copy some of the exteNd template files from the frames directory into the css directory Refer to the Identity Manager Accessory Portlet Reference Guide http developer n...

Page 278: ...278 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 279: ...e 307 Chapter 33 Implementing the Internet Agent in a Heartbeat Cluster on page 325 Chapter 34 Implementing WebAccess in a Heartbeat Cluster on page 343 Chapter 35 Implementing GroupWise Monitor in a...

Page 280: ...280 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 281: ...sure you have a solid understanding of the environment into which you are installing GroupWise Heartbeat is an open source project that provides clustering services on Linux The following Web sites pr...

Page 282: ...cation among them and performs other basic cluster setup For convenience and for best performance with GroupWise add the following lines to the ha cf file use_logd yes keepalive 2 deadtime 30 warntime...

Page 283: ...as when maintenance is required cibadmin lets you modify the configuration information in the cib xml file GUI HA Management Client usr lib heartbeat haclient py http www linux ha org GuiGuide When y...

Page 284: ...rce fencing in your cluster Node fencing locks resources away from a node whose status is uncertain Resource fencing ensures exclusive access to a given resource and provides finer granularity so that...

Page 285: ...ents in a Heartbeat cluster A new GroupWise system consisting of the primary domain and the initial post office A new secondary domain A new post office GroupWise Message Transfer Agent MTA and Post O...

Page 286: ...the system resources to run all of your GroupWise system in a cluster you must decide which parts have the most urgent need for the high availability provided by clustering Here are some suggestions P...

Page 287: ...econdary IP address that will be used by the MTA that services the domain The domain directory and secondary IP address must be available before the MTA can start Typically Heartbeat resources and gro...

Page 288: ...0 3 Planning a New Clustered Domain The considerations involved in planning a new domain in a clustering environment are essentially the same as for any other environment Primary Domain If you are set...

Page 289: ...The initial post office in a new GroupWise system is planned on the Basic GroupWise System Worksheet in the GroupWise 7 Installation Guide To plan additional new post offices review Planning a New Pos...

Page 290: ...o do so in Chapter 32 Setting Up a Domain and a Post Office in a Heartbeat Cluster on page 307 30 6 Considering How to Install and Configure the Linux Agents in a Cluster There are several cluster spe...

Page 291: ...oups should not all fail over together to the same node Instead the resource groups should be distributed across multiple nodes in the cluster This prevents any one node from shouldering the entire pr...

Page 292: ...score of INFINITY in the colocation constraint HEARTBEAT CLUSTERING WORKSHEET Under Item 9 Cluster Resource Group Constraints for Domain list the nodes that might need to mount the domain The MTA migh...

Page 293: ...30 7 2 GroupWise Clustering Worksheet on page 294 30 7 1 Heartbeat Clustering Worksheet Item Explanation 1 HA Management Client Password Specify the password you use to access the GUI HA Management Cl...

Page 294: ...n page 136 8 Cluster Resource for Post Office Post Office Name Specify the name of the cluster resource group where the GroupWise post office will reside along with the name of the post office For mor...

Page 295: ...or the post office Specify the directory on the resource group partition where you want to create the post office Specify the mount point where each node will mount the post office directory For more...

Page 296: ...296 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 297: ...ion 31 5 Starting the Native Heartbeat Resources on page 305 31 1 Starting the HA Management Client 1 On a node in the cluster become the hacluster user in a terminal window 2 If you have not yet set...

Page 298: ...he HA Management Client select Resources then click Add New Item 2 In the Item Type drop down list select group then click OK 3 In the ID field specify the name of the GroupWise resource group Heartbe...

Page 299: ...native resources GroupWise resources for domains and post offices must be created after you install the GroupWise software so that the GroupWise script is available to enhance the capabilities of the...

Page 300: ...8 Repeat Step 1 through Step 7 to create an EVMS container resource in each cluster resource group 9 Continue with File System Resources 31 3 2 File System Resources In the HA Management Client 1 Sel...

Page 301: ...s 31 3 3 IP Address Resources In the HA Management Client 1 Select a new cluster resource group then click Add New Item 2 In the Item Type field select native then click OK 3 In the Resource ID field...

Page 302: ...on page 302 Section 31 4 2 Order Constraints on page 303 Section 31 4 3 Colocation Constraints on page 304 For more information about Heartbeat constraints consult the Heartbeat documentation that is...

Page 303: ...cluster resource group to run on a regular basis If the place constraint has a score of 50 you would select the node where you want the cluster resource group to fail over if its initial node fails 6...

Page 304: ...select colocation then click OK 3 Specify the unique ID for the colocation constraint select a resource group select another resource group that you always want to run on the same node as the first r...

Page 305: ...ontainer resource then click Start Resource 2 Select the file system resource then click Start Resource 3 Select the IP address resource then click Start Resource When a resource starts successfully t...

Page 306: ...306 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 307: ...nd an initial post office owned by the primary domain You might be creating your primary domain and initial post office in the same cluster resource group or in two different cluster resource groups A...

Page 308: ...the MTA and POA network address information use their secondary IP addresses GroupWise Clustering Worksheet item 3 for the MTA and item 5 for the POA The information you provide is used to configure...

Page 309: ...for best MTA performance in the cluster 6 Make sure you are still connected to the primary domain 7 Rebuild the domain database for the new domain following the steps provided in Rebuilding Domain or...

Page 310: ...on about these repetitive POA activities see Performing Nightly User Upkeep Regulating Indexing and Scheduling Database Maintenance in Post Office Agent in the GroupWise 7 Administration Guide 8 Make...

Page 311: ...post office In these circumstances follow the instructions in Section 32 4 6 Setting Up New Instances of the Agents without Installing the Agent Software on page 319 instead of running the GroupWise I...

Page 312: ...g in a cluster The ip startup switch is set to the secondary IP address for the cluster resource group where the domain and post office are located This ensures that the MTA and the POA run with the s...

Page 313: ...stallation Program on Subsequent Nodes 32 4 2 Running the GroupWise Installation Program on Subsequent Nodes 1 In the HA Management Client select a different node where you want to run the agents Hear...

Page 314: ...ick Next All GroupWise agents that you have installed from the software distribution directory are listed based on the information stored in the clusterimport conf file 5 Select the GroupWise agents t...

Page 315: ...roupWise Agents in the GroupWise 7 Installation Guide 7 Repeat Step 1 through Step 6 for each node where you want the agents to be able to fail over Heartbeat Clustering worksheet item 9 for a domain...

Page 316: ...ain or post office GroupWise Clustering Worksheet item 2 or item 4 For a domain the identifier is the domain name For a post office the identifier is the name of the post office followed by the name o...

Page 317: ...is online again 1 In the HA Management Client select each GroupWise resource group click Parameters then click Add Parameter 2 In the Name field specify resource_stickiness 3 In the Value field speci...

Page 318: ...agents on all of the nodes where the domain and post office can fail over continue with Changing Agent Paths to Locations on GroupWise Partitions 32 4 5 Changing Agent Paths to Locations on the Share...

Page 319: ...Office with SSL Connections to the POA in Post Office Agent in the GroupWise 7 Administration Guide 1 On the shared storage partition of the cluster resource group where the post office is located cre...

Page 320: ...y Service for the Linux GroupWise Agents in Installing GroupWise Agents in the GroupWise 7 Installation Guide 8 As if you had run the GroupWise Installation program skip back to Section 32 4 3 Creatin...

Page 321: ...1 Recording Cluster Specific Information for a Post Office and Its POA on page 322 Recording Cluster Specific Information for a Software Distribution Directory on page 322 Recording Cluster Specific I...

Page 322: ...ly to save the description 8 Click Network Address 9 In the TCP IP Address field provide the secondary IP address that you provided in the GroupWise Installation program for use with the ip switch in...

Page 323: ...of their normal shutdown procedure However as a result no database repair is required when the agents start up again in their new location 32 7 What s Next Now that you have at least one GroupWise do...

Page 324: ...324 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 325: ...net Agent in a Heartbeat Cluster on page 339 Section 33 5 Internet Agent Clustering Worksheet on page 340 33 1 Planning the Internet Agent in a Heartbeat Cluster A major system configuration differenc...

Page 326: ...the MTA installation later When you have completed the Domain Worksheet transfer the key information from the Domain Worksheet to the Internet Agent Clustering Worksheet IMPORTANT Do not create the n...

Page 327: ...roup can fail over You must install the Internet Agent software on all of the nodes where you want the Internet Agent to be able to fail over For a review of the fan out failover principle see Section...

Page 328: ...nstalling the Internet Agent configure your firewall as needed to handle the Internet Agent s use of primary and secondary IP addresses when sending and receiving messages 33 1 7 Planning the MTA Inst...

Page 329: ...he IP address resource for the cluster resource group Internet Agent Clustering Worksheet item 3 as described in Section 31 3 Creating Native Heartbeat Resources on page 299 As opposed to native Heart...

Page 330: ...t Agent for SSL on page 336 Enabling Internet Addressing for Your Clustered GroupWise System on page 337 Verifying Internet Agent Object Properties on page 337 Running the Internet Agent Installation...

Page 331: ...ns with the same IP address regardless of which node it runs on The log startup switch is set to a location on the shared storage partition mount_point groupwise agents log so that Internet Agent logg...

Page 332: ...3 then click Make the Node Active 2 From the software distribution directory you created in Step 6 in Section 14 1 Setting Up a New GroupWise System in a Linux Cluster on page 143 start the GroupWise...

Page 333: ...ce d novell directory on the node for use by the HA Management Client Because the agent startup files and log files are stored on the shared storage partition they do not need to be customized for eac...

Page 334: ...Wise added this item to the list 6 In the Parameters list set the value of the object_name parameter to the identifier for the Internet Agent Internet Agent Clustering Worksheet item 4 For the Interne...

Page 335: ...High Availability Service can work together to keep the Internet Agent running on Linux 6 Continue with Preventing Internet Agent Failback Preventing Internet Agent Failback If you do not want the Int...

Page 336: ...ame for example gwia conf then that Internet Agent has not yet been initialized by being run manually To resolve the problem you can run the Internet Agent manually on that node or you can replace the...

Page 337: ...ount Point Directory on page 337 Verifying Post Office Links on page 338 Forcing Use of the Internet Agent Secondary IP Address on page 338 Accessing Internet Agent Object Properties 1 In ConsoleOne b...

Page 338: ...Heartbeat Cluster After you have installed and configured the Internet Agent in your Heartbeat cluster you can use the following methods to test whether the Internet Agent fails over as expected In th...

Page 339: ...nternet Agent Domain and Its MTA on page 339 Recording Cluster Specific Information about the Internet Agent on page 339 Recording Cluster Specific Information about the Internet Agent Domain and Its...

Page 340: ...y slow to shut down properly as it finishes its normal processing and stops its threads For a busy Internet Agent you might need to wait several minutes for it to shut down properly 33 5 Internet Agen...

Page 341: ...partition where you want to create the new domain Specify the mount point on each node where you plan to mount the domain For more information see Section 15 1 1 Planning a Domain for the Internet Age...

Page 342: ...342 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 343: ...tbeat Cluster on page 356 Section 34 5 Managing the WebAccess Agent in a Heartbeat Cluster on page 356 Section 34 6 WebAccess Agent Clustering Worksheet on page 358 34 1 Understanding the WebAccess Co...

Page 344: ...Agent The considerations involved in planning a domain for the WebAccess Agent are much the same as planning any other domain In preparation review Planning a New Domain then print and fill out the Do...

Page 345: ...resource group mounted and active If a cluster resource group s initial node fails the resource group fails over to another node in the cluster You should customize the Heartbeat constraints for each...

Page 346: ...TANT Do not install the WebAccess Agent software until you are instructed to do so in Section 16 3 Setting Up the WebAccess Agent in a Linux Cluster on page 190 34 2 7 Planning the WebAccess Applicati...

Page 347: ...nodes where the WebAccess Agent and its domain can fail over WebAccess Agent Clustering Worksheet item 5 as described in Section 31 4 Creating Heartbeat Constraints on page 302 5 Refine the configurat...

Page 348: ...roperties on page 355 Running the WebAccess Agent Installation Program on the Initial Node 1 Make sure that the WebAccess Agent software is available in the software distribution directory you created...

Page 349: ...nt has already been installed on this node the gwha conf file is updated to include the WebAccess Agent If it is not already present the OCF Resource Agent script GroupWise is installed in the usr lib...

Page 350: ...the WebAccess Agent software on the node as usual but do not use the Configure option You will use the Import Clustering Data option instead of the Configure option 4 On the main page of the Installa...

Page 351: ...ities of the HA Management Client Because the agent startup files and log files are stored on the shared storage partition they do not need to be customized for each node 6 Continue with Creating and...

Page 352: ...ng Automatic WebAccess Agent Restart Enabling Automatic WebAccess Agent Restart If you want Heartbeat to automatically restart a WebAccess Agent that has stopped 1 In the HA Management Client select t...

Page 353: ...see that the WebAccess Agent stopped successfully test it by starting it as a daemon as described in Starting the Linux GroupWise Agents as Daemons in Installing GroupWise Agents in the GroupWise 7 In...

Page 354: ...tered WebAccess Agent for SSL Configuring the Clustered WebAccess Agent for SSL If you plan to enable SSL as described in Securing WebAccess Agent Connections with SSL in WebAccess in the GroupWise 7...

Page 355: ...l post offices serviced by the WebAccess Agent 3 Verify that the Links column displays the secondary IP addresses of the cluster resource group where post offices reside not the IP addresses of any no...

Page 356: ...t Installation on Each Node on page 353 for troubleshooting assistance If you have set up your Heartbeat cluster in a test situation first you can also use the following methods for testing WebAccess...

Page 357: ...the cluster resource group and shared storage partition where the domain is located 3 Click OK to save the WebAccess Agent domain description 4 Select the WebAccess Agent Domain object to display its...

Page 358: ...node by its DNS hostname and the IP address that it is physically configured with For more information see Section 34 2 1 Planning a Cluster Resource Group for the WebAccess Agent on page 344 2 WebAcc...

Page 359: ...g a Domain for the WebAccess Agent on page 188 7 MTA Network Information Secondary IP address Message transfer port default 7100 HTTP port default 7180 Record the MTA network address information that...

Page 360: ...360 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 361: ...Implementing GroupWise Monitor in a Heartbeat Cluster 35 361 novdocx en 11 July 2008 35 Implementing GroupWise Monitor in a Heartbeat Cluster Monitor is not currently supported in a Heartbeat cluster...

Page 362: ...362 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 363: ...t Cluster To back up GroupWise data in a Heartbeat cluster use the GroupWise Database Copy DBCopy utility to copy the data from the live GroupWise system to a static location for backup For more infor...

Page 364: ...364 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 365: ...It is very important to update at the same time all nodes where each domain and post office can fail over because each domain and post office should be serviced by only one version of the agent softwa...

Page 366: ...366 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 367: ...nts have been running in the past and have been starting automatically use the following command to make sure that they do not start automatically in the future chkconfig grpwise off In a cluster the...

Page 368: ...upWise libraries see Section 13 5 Planning a New Library for a Clustered Post Office on page 137 Add other components to your clustered GroupWise system as needed following the instructions in Chapter...

Page 369: ...Heartbeat Cluster Because the Messenger agents are not associated with GroupWise domains or post offices the Messenger agents are easier to implement in a cluster than are the GroupWise agents The Mes...

Page 370: ...me and the IP address that it is physically configured with Under Item 2 Messaging Agent Cluster Resource Group specify the name of the cluster resource group to hold the native and Messenger resource...

Page 371: ...page 372 Section 39 2 3 Changing Messenger Paths to Locations on the Messenger Partition on page 376 39 2 1 Setting Up Native Heartbeat Resources for the Messenger Agents 1 Start the HA Management Cl...

Page 372: ...g Worksheet item 2 in order to mount the shared storage partition 2 From the Messenger 2 Administrator for Linux CD run the Messenger Installation program following the steps provided in Starting the...

Page 373: ...g and Configuring Messenger Cluster Resources for the Messenger Agents Creating and Configuring Messenger Cluster Resources for the Messenger Agents Now that you have installed the Messenger agent sof...

Page 374: ...atic Messaging Agent Restart Enabling Automatic Messaging Agent Restart If you want Heartbeat to automatically restart a Messaging Agent that has stopped 1 In the HA Management Client select the Messe...

Page 375: ...l Messenger System in the Messenger 2 0 Installation Guide etc init d novell nmma start etc init d novell nmaa start etc init d novell nmma status etc init d novell nmaa status 2 Stop the Messenger ag...

Page 376: ...g on Setting the Store Path on page 376 Setting the Messaging Agent Queue Path on page 376 Setting the Archive Agent Queue Path on page 377 Setting the Messaging Agent Log Path on page 377 Setting the...

Page 377: ...eated in var opt novell messenger aa queue but you need the queue directory to be located on the shared storage partition 1 Choose a directory for the Archive Agent queue and create that directory on...

Page 378: ...Using the crm_resource utility http www linux ha org v2 AdminTools crm_resource manually migrate a node where a Messenger agent is running If you receive the error Unmanaged on node see Step 4 in Test...

Page 379: ...Cluster on page 229 4 Native Heartbeat Resources EVMA container File system Secondary IP address List names for the native Heartbeat resources and the values for their parameters to be used in the Me...

Page 380: ...ent Network Information Secondary IP address Record the Archive Agent network address information that you will need to install the Messaging Agent For more information see Section 22 1 2 Selecting th...

Page 381: ...01 Chapter 43 Implementing the Internet Agent in a Microsoft Cluster on page 413 Chapter 44 Implementing WebAccess in a Microsoft Cluster on page 423 Chapter 45 Implementing GroupWise Gateways in a Mi...

Page 382: ...382 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 383: ...he cluster that is actively running programs An active node makes its resources available in the cluster passive node A node in the cluster that is not currently running programs but is waiting for an...

Page 384: ...r 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 For exa...

Page 385: ...ess component configuration alternatives are explained For example you might want the domain and post office together in the same resource group or in separate resource groups You might want to instal...

Page 386: ...ise client users when they are unavailable unless users in different post offices happen to be actively engaged in an e mail discussion when the MTA goes down On the other hand domains and their MTAs...

Page 387: ...r the Domain Worksheet to the System Clustering Worksheet IMPORTANT Do not create the new domain until you are instructed to do so in Chapter 3 Setting Up a Domain and Post Office in a NetWare Cluster...

Page 388: ...ce resource group will be known on the network regardless of which node it is active on IP Address The virtual IP address that will be associated with the network name regardless of which node the dom...

Page 389: ...so this limitation does not apply to POAs and MTAs 41 6 Planning Shared Administrative Resources Depending on your administrative needs you might or might not want to set up shared administrative res...

Page 390: ...indows workstation Figure 41 1 Novell Client Preferences Property Page Short name resolution methods that pertain to your clustered GroupWise system are discussed below Table 41 1 Short Name Resolutio...

Page 391: ...me there is a possibility of two of the same type of agent running on the same node it is important that each agent use a cluster unique port number even though each agent is using the unique IP addre...

Page 392: ...e example also illustrates that the MTA the POA and the Internet Agent use different port numbers for agent ports and HTTP ports In contrast the WebAccess Agent uses the same port number for the agent...

Page 393: ...p the GroupWise agents in the cluster 41 8 2 Deciding Where to Install the Agent Software In a Microsoft cluster the agents must run as Windows services When you install the Windows MTA and POA you ca...

Page 394: ...makes them easy to find If you change information in the agent startup files you only need to change it in one place not on every node in the resource group s possible owners list If you want to back...

Page 395: ...stallation Aside from the cluster specific issues discussed in the preceding sections the considerations involved in planning to install the GroupWise Windows agents are the same in a Microsoft cluste...

Page 396: ...he same node in order to fail over together Under Item 3 Installation Path take into account your decision based on Deciding Where to Install the Agent Software on page 393 Under Item 8 Installation O...

Page 397: ...ssible owners Specify the information for the post office resource group For more information see Section 41 3 Planning a New Clustered Post Office on page 387 6 IP Address Resolution Methods eDirecto...

Page 398: ...orage Area Access POA user startup switch setting POA password startup switch setting If you need a library for a clustered post office mark where you want to create its document storage area and prov...

Page 399: ...m Clustering Worksheet item 6 3 MTA Service Resource Service name Possible owners Resource dependencies List other nodes in the cluster where the domain resource group could fail over and any resource...

Page 400: ...n POA IP address POA client server port POA message transfer port POA HTTP port Gather the POA network address information from the Network Address Worksheet on page 398 For more information see Plann...

Page 401: ...09 Section 42 7 Managing Your Clustered GroupWise System on page 409 Section 42 8 What s Next on page 411 42 1 Preparing the Cluster for GroupWise After you have set up your Microsoft cluster and beco...

Page 402: ...One 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 clus...

Page 403: ...visor to set up your initial GroupWise system following the steps provided in NetWare and Windows Setting Up a Basic GroupWise System in Installing a Basic GroupWise System in the GroupWise 7 Installa...

Page 404: ...install the agents to first 6 In ConsoleOne connect to the primary domain in your GroupWise system as described in Connecting to a Domain in Domains in the GroupWise 7 Administration Guide 7 Create th...

Page 405: ...roup as Domain under System Clustering Worksheet item 4 map a drive to the shared disk of the domain resource group or Map a drive to the shared disk of the post office resource group System Clusterin...

Page 406: ...location System Clustering Worksheet item 7 through the shared disk you accessed in Step 1 to the post office directory you created in Step 2 above The database rebuild is necessary in order to transf...

Page 407: ...If you plan to install the agent software to each node in the cluster create the c grpwise directory on the drive accessed in Step 2 4 Start the Agent Installation program following the steps provide...

Page 408: ...POA needs to access a remote document storage area that is outside the cluster add the user and password startup switches under System Clustering Worksheet item 9 in order to provide a user name and p...

Page 409: ...er 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 kee...

Page 410: ...ort numbers used by the POA This information appears on the POA console no matter which node in the cluster it is currently running on 7 Click OK to save the POA description 8 If necessary continue wi...

Page 411: ...However as a result no database repair is required when the agents start up again in their new location Continue with What s Next 42 8 What s Next Now that you have at least one GroupWise domain and...

Page 412: ...412 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 413: ...ent is that you need to create a separate domain to house each GroupWise gateway including the Internet Agent The Internet Agent is faster and more stable when it runs on the same server with its doma...

Page 414: ...ent If you plan to have more than one Internet Agent in the cluster they must never fail over to the same node To ensure successful short name resolution add entries for the Internet Agent network nam...

Page 415: ...ive you can configure the Internet Agent to use its resource group IP address for sending as well as receiving messages Setup instructions for this configuration are provided in Forcing Use of the Int...

Page 416: ...GroupWise Internet Agent in the GroupWise 7 Installation Guide You need this information as you install the Internet Agent in your cluster IMPORTANT Do not install the Internet Agent software until y...

Page 417: ...tem Clustering Worksheet then return to this point Do not create any post offices in the Internet Agent domain Continue with Installing the MTA for the Internet Agent Domain 43 2 3 Installing the MTA...

Page 418: ...complete 6 Repeat Step 4 and Step 5 mapping a drive to each node in the cluster Even if you installed the Internet Agent software to a shared disk you need to repeat the installation process for each...

Page 419: ...twork name of the domain resource group not the name of a node in the cluster 3 Make changes if necessary 4 Continue with Verifying the Reference to the Network Name in Directory Paths Verifying the R...

Page 420: ...t Agent in a cluster you should consider some long term management issues Section 43 3 1 Updating GroupWise Objects with Cluster Specific Descriptions on page 420 Section 43 3 2 Knowing What to Expect...

Page 421: ...ter unique port numbers used by the Internet Agent 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...

Page 422: ...ore information see Deciding Where to Install the Internet Agent and Its MTA on page 415 5 MTA Network Information MTA IP address MTA message transfer port MTA live remote port MTA HTTP port Gather th...

Page 423: ...alling GroupWise WebAccess in the GroupWise 7 Installation Guide As you plan WebAccess in a clustering environment you must keep in mind that you will plan and set up two separate WebAccess components...

Page 424: ...ing a New Domain for the WebAccess Agent The considerations involved in planning a domain for the WebAccess Agent are much the same as planning any other domain In preparation review Planning a New Do...

Page 425: ...o install the MTA and POA you should already have determined the IP address and cluster unique port numbers for the WebAccess Agent and its MTA as you filled out the Network Address Worksheet on page...

Page 426: ...involved in planning to install WebAccess are the same in a clustering environment as for any other environment Review Planning GroupWise WebAccess then print and fill out the GroupWise WebAccess Ins...

Page 427: ...ervices resources WebAccess Clustering Worksheet item 1 as planned in Planning the WebAccess Resource Group on page 425 2 To ensure successful short name resolution add entries for the WebAccess Agent...

Page 428: ...ries to retrieve information for WebAccess client users 1 Map a drive to the shared disk of the WebAccess resource group WebAccess Clustering Worksheet item 1 2 Map a drive to c on the first node in t...

Page 429: ...ebAccess Agent and the WebAccess clients Web browsers To install the WebAccess Application 1 Map a drive to the shared disk of the WebAccess resource group WebAccess Clustering Worksheet item 1 where...

Page 430: ...esource group are separate resource groups that could fail over to different nodes at different times To thoroughly test your WebAccess installation 1 Make sure the initial combination of WebAccess re...

Page 431: ...rt numbers used by its MTA You might also want to include cluster specific information about the WebAccess Application such as the resource group IP address of the Web server where the WebAccess Appli...

Page 432: ...having to re authenticate As with the MTA and the POA migration of the WebAccess Agent takes longer than failover However the WebAccess Agent restarts quickly so that users are able to reconnect quic...

Page 433: ...ion where you will consolidate the MTA startup files on the shared disk of the WebAccess resource group For more information see Deciding Where to Install the WebAccess Agent and Its MTA on page 426 4...

Page 434: ...luster on page 424 8 Web Server IP Address Record the secondary IP address for the Web server in the cluster For more information see Setting Up Your Web Server in the Microsoft Cluster on page 424 9...

Page 435: ...upWise gateway The gateway domain should be created in its own resource group This enables the gateway to fail over independently from other GroupWise components If you have set up the Internet Agent...

Page 436: ...436 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 437: ...about agents to monitor from a domain database wpdomain db This provides the resource group IP address of each agent When an agent fails over or migrates to a different node its status in Monitor dis...

Page 438: ...438 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 439: ...ant to back up your GroupWise system while it is running you must use backup software that can back up open files If your backup software cannot back up open files then you must stop all GroupWise age...

Page 440: ...440 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 441: ...which domains and post offices you will move to which shared disks Review Planning Cluster Unique Port Numbers for Agents in the Cluster on page 391 and fill out the Network Address Worksheet on page...

Page 442: ...the instructions in Chapter 43 Implementing the Internet Agent in a Microsoft Cluster on page 413 Chapter 44 Implementing WebAccess in a Microsoft Cluster on page 423 Chapter 45 Implementing GroupWise...

Page 443: ...3 Messenger Clustering Worksheet on page 447 lists all the information you need as you set up the Messenger agents in a clustering environment You should print the worksheet and fill it out as you com...

Page 444: ...install the Messenger agents Skip to Planning the Messenger Agent Installation on page 445 MESSENGER CLUSTERING WORKSHEET Under Item 5 Installation Location for Messenger Administration mark whether y...

Page 445: ...m 4 Resource Group for Messenger Agents on the Messenger Clustering Worksheet Under Item 12 Server Address on the Messenger System Worksheet If you are installing the Messenger agents to each node in...

Page 446: ...e Messenger agent startup files to the planned location on the shared disk then delete them from the c novell nm ma and c novell nm aa directories on each node to avoid future confusion 3 Make each no...

Page 447: ...ion through the drive mapped in Step 2 above When you specify the ConsoleOne directory be sure to browse to the location through the drive mapped in Step 1 above On the Setup Complete page do not sele...

Page 448: ...ministration Administrator workstation s Shared disk Mark the location where you want to install the Messenger snap in to ConsoleOne For more information see Planning Messenger Administration on page...

Page 449: ...e 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 P...

Page 450: ...450 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 451: ...ow steps similar to the following NOTE Steps might vary depending on the versions of Windows and Outlook Express installed on the workstation 1 In Outlook Express click Tools Accounts Add Mail 2 Follo...

Page 452: ...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 S...

Page 453: ...Office they can continue to use POP or IMAP in it to access their GroupWise mailboxes In order for users to access their GroupWise mailboxes from Outlook they must configure Windows to access their G...

Page 454: ...can now access your GroupWise mailbox using Microsoft Outlook by selecting the profile you just created For additional functionality you can install the GroupWise Connector for Microsoft Outlook avail...

Page 455: ...ell GroupWise 7 Section 52 1 GroupWise Features Available in Evolution on page 455 Section 52 2 Configuring Evolution on page 456 52 1 GroupWise Features Available in Evolution Evolution connecting to...

Page 456: ...ution they must configure Evolution to access their GroupWise accounts 1 Click Edit Preferences then click Mail Accounts 2 Click Add 3 On the Identity page type your e mail address then click Forward...

Page 457: ...messages in the Inbox on the server 10 Select if you want to check new messages for junk content 11 Select if you want to only check for junk messages in the Inbox folder 12 Select if you want to aut...

Page 458: ...458 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 459: ...s 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 53 GroupWise...

Page 460: ...460 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 461: ...es and SyncML devices The GroupWise Mobile Server includes the following modules from Intellisync E mail Accelerator excluding POP3 IMAP Exchange Connector Lotus Notes Connector Workgroup and PC Monit...

Page 462: ...462 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 463: ...e 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 i...

Page 464: ...464 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 465: ...zing anything in Outlook such as e mail calendar tasks or notes in either ActiveSync or PocketMirror 55 2 Downloading the Software GroupWise PDA Connect 1 0 is available for download at the Novell Pro...

Page 466: ...466 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 467: ...rding to the date when the Interoperability Guide was republished Within each dated section the updates are listed by the section title The GroupWise 7 Interoperability Guide has been updated on the f...

Page 468: ...468 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 469: ...Conferencing Novell Teaming and Conferencing on page 243 Updated the section to correspond with Teaming and Conferencing 1 0 Support Pack 3 Section 25 1 3 Adding the New Web Server Accelerator to the...

Page 470: ...470 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 471: ...uster where the WebAccess Agent is installed Using TSAFSGW in a NetWare 6 x Cluster on page 112 Corrected the description of the functionality of TSAFSGW in a cluster Microsoft Clustering Services Pla...

Page 472: ...472 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 473: ...08 C October 24 2007 Location Change Novell Teaming and Conferencing Novell Teaming and Conferencing on page 243 Added a new section about integrating eDirectoryTM and GroupWise with the Novell Teamin...

Page 474: ...474 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 475: ...opying LDAP and QuickFinder Files to the Messenger Volume on page 125 Improved the instructions for handling LDAP and QuickFinder files after installing the Messenger agents in a cluster Heartbeat on...

Page 476: ...476 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 477: ...ovdocx en 11 July 2008 E September 29 2006 Location Change Novell Cluster Services on NetWare Section 3 5 2 Editing Clustered Agent Startup Files on page 52 Mentioned use of the user and password star...

Page 478: ...478 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 479: ...raditional file system disk partitions Configuring the WebAccess Agent Cluster Resource to Load and Unload the WebAccess Agent and Its MTA on page 196 Added new examples of load and unload scripts for...

Page 480: ...480 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 481: ...ity associated with the vserver switch Chapter 9 Updating a GroupWise System in a NetWare Cluster on page 115 Added a new section about updating GroupWise software in a NetWare cluster Configuring the...

Page 482: ...ram on the Preferred Node on page 172 Explained that you install the Internet Agent software from the software distribution directory not the CD explained the new cluster resource options on the Serve...

Page 483: ...ling the Messenger agents in a cluster Running the Messenger Installation Program on Subsequent Nodes on page 232 Explained that the Messenger Installation program gathers agent configuration informat...

Page 484: ...484 GroupWise 7 Interoperability Guide novdocx en 11 July 2008...

Page 485: ...Novell exteNd on page 277 Added information about Novell exteNdTM compatibility with GroupWise WebAccess and provided a link to the exteNd documentation that explains how to configure exteNd for use...

Reviews:

No comments

Brands by name

0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Popular brands

Load more brands