To create a user for the agents to log in as:

1. In ConsoleOne, create a new user (such as GWAgents).

2. Provide a password for that user (such as GWise).

3. Grant that user the following rights to all domain, post office, and document storage directories:

   • Read or execute files

   • Write to files

   • Create files or directories

   • Erase files or directories

   • Modify files (rename or change attributes)

   • File scan

4. After you install the agent software, add the /user and /password startup switches to the agent startup files so that the agents can log in to the remote server as the user you have created.

To configure the GroupWise agents to switch users after startup:

1. Make sure you are logged in as root.

2. Select a Linux user for the agents to run as and make sure that the user is listed in the /etc/passwd file.

   You might want to create a new user specifically for this purpose, perhaps named gwagents.

3. Change to the groupwise directory under /etc:

   cd /etc/opt/novell/groupwise
   

4. Create a new agents directory, then change to that directory:

   mkdir agents
   cd agents
   

5. Create a file named uid.conf.

6. Type the selected username in the file, for example:

   gwagents
   

7. Stop and then start the agents.

   While starting as root, the agents automatically change the ownership of the domain and post office directory structures from root to the user you specified in the uid.conf file. Then they switch users and run as the user you specified, rather than as root.

   If you list the agent processes, you can observe that they are no longer running as root.

   If the post office and domain are located on different servers, you must complete the above steps on each server.

   IMPORTANT:All agents running on the same server must run as the same user.

To configure the agents to switch users after startup and provide access to an NSS volume:

1. Select or create an eDirectory user for the agents to run as.

   You might want to create a new user specifically for this purpose, perhaps named gwagents.

   1. From the Open Enterprise Server Welcome page in your Web browser, expand Network Management, then click iManager 2.5.x.

   2. In the iManager Links box, click Open Novell iManager 2.5.

   3. To log in to iManager, specify a username, a password, and a tree.

   4. In the left pane, expand Users, then click Create User.

   5. Provide the required information, then click OK.

      The user does not need a password

2. LUM-enable the user you just created.

   1. In the left pane, expand Linux User Management, then click Enable User for LUM.

   2. Browse to and select the user you just created, then click OK.

   3. Select the primary group for the user to belong to (for example, admingroup).

   4. Change /bin/bash to /bin/false because the user does not need a shell.

   5. Click OK to LUM-enable the user.

3. In a terminal window, change to the groupwise directory under /etc:

   cd /etc/opt/novell/groupwise
   

4. Create a new agents directory, then change to that directory.

   mkdir agents
   cd agents
   

5. Create a file named uid.conf

6. Type the selected username in the file, for example:

   gwagents

7. Use the following command to grant the user the required rights to the directories that the agents need to access on the local server:

   rights -f /directory -r rwcemf trustee user.context.tree
   

   The POA needs access to the post office directory. The MTA and the Internet Agent need access to the domain directory.

8. Stop and then start the agents.

   While starting as root, the agents automatically change the ownership of the domain and post office directory structures from root to the user you specified in the uid.conf file. Then they switch users and run as the user you specified, rather than as root.

   If you list the agent processes, you can observe that they are no longer running as root.

   If the post office and domain are located on different servers, you must complete the above steps on each server.

   IMPORTANT:All agents running on the same server must run as the same user.

To set up the High Availability service:

1. In a terminal window, become root by entering sux and the root password.

   The sux command enables the X Window System, which is required for running the GUI GroupWise agent server consoles.

2. Before starting to configure the High Availability service, test the agents by starting and stopping them manually with a user interface so that their agent server consoles display.

   1. Change to the root directory of the Linux server.

   2. Start the GroupWise agents manually, including providing the full path to the executable and including the --show switch, to make sure that they are set up and configured correctly.

      /opt/novell/groupwise/agents/bin/gwpoa --show @post.poa
      /opt/novell/groupwise/agents/bin/gwmta --show @dom.mta
      /opt/novell/groupwise/agents/bin/gwia --show @gwia.cfg
      /opt/novell/groupwise/agents/bin/gwinter --show @webac70a.waa
      

   3. After verifying that the agents start correctly, stop the agents.

3. If you use SSL, you need to modify the High Availability service configuration file (gwha.conf).

   1. Change to the /etc/opt/novell/groupwise directory.

   2. Edit the gwha.conf file in a text editor

   3. Under the [gwha] section, fill in the fields as follows:

      [gwha]
      ssl      = yes
      key      = filename.key
      cert     = filename.crt
      password = password
      

   4. Save the file, then exit the text editor.

4. If you want to control how the script manages starting and stopping the agents, modify the delay = and wait = settings in the High Availability service configuration file (gwha.conf).

   The delay = setting controls the length of time between when the script issues the command to start an agent and when the script displays a message indicating that the agent has started. The default delay time is 2 seconds. Under certain circumstances, an agent could encounter a problem and fail to start after 2 seconds. In this case, you would receive the success message but the agent would not be running. You need to increase the delay = setting to accommodate the length of time it typically takes for the agent to start successfully on your system.

   The wait = setting controls the length of time between when the script issues the command to stop an agent and when the script kills the agent if the agent has not yet stopped. The default wait time is 10 seconds. Under certain circumstances, an agent could take longer than 10 seconds to perform a normal shutdown, and killing the agent under those circumstances would not be appropriate. You need to increase the wait = setting to accommodate the length of time it usually takes for the agent to shut down. A message notifies you if the script kills an agent because its shutdown exceeds the wait = setting.

   The default settings are usually appropriate, so you do not need to change them unless you frequently encounter problems with starting or stopping an agent using the script.

   1. Change to the /etc/opt/novell/groupwise directory.

   2. Edit the gwha.conf file in a text editor

      Each agent has its own section in the file, for example:

      [Waltham2]
      server = /opt/novell/groupwise/agents/bin/gwmta
      command = /etc/init.d/grpwise
      startup = waltham2.mta
      delay = 2
      wait = 10
      

   3. Change the delay = and wait = settings as needed.

   4. Save the file, then exit the text editor.

5. If you want the script to start the agents with a user interface on the Linux server, add the show = setting in the High Availability service configuration file (gwha.conf). This is equivalent to using the --show startup switch on the command line when starting the agent.

   1. Change to the /etc/opt/novell/groupwise directory.

   2. Edit the gwha.conf file in a text editor

      Each agent has its own section in the file, for example:

      [Waltham2]
      server = /opt/novell/groupwise/agents/bin/gwmta
      command = /etc/init.d/grpwise
      startup = waltham2.mta
      delay = 2
      wait = 10
      

   3. Add show = yes to the section for each agent that you want to start with a user interface.

      If you need to eliminate the user interface, use show = no or delete the show = line from the file.

   4. Save the file, then exit the text editor.

6. Enable the High Availability service:

   1. In YaST, click Network Services > Network Services (inetd).

   2. If necessary, select Enable to activate the list of services.

   3. Scroll down to the gwha line, select it, then click Toggle Status (On or Off) to change the status to On.

   4. Click Finish.

7. Start the agents as daemons.

   1. Change to the /etc/init.d directory.

   2. Enter the following command to start the GroupWise agents that are installed on the server:

      ./grpwise start
      

   3. Use the following command to verify agent status:

      ./grpwise status
      

      For more information about using the grpwise script, see Starting the Linux GroupWise Agents as Daemons

8. Create a new user and associated password on your Linux server to represent the High Availability service.

   You might name it gwha.

9. Continue with Configuring the Monitor Agent to Communicate with the High Availability Service.

1. Start the Monitor Agent with the --hauser and --hapassword startup switches.

   If you use the grpwise-ma script to start the Monitor Agent, as described in Starting the Linux Monitor Agent as a Daemon, you can edit it to include the switches:

   1. Change to the /etc/init.d directory, then edit the grpwise-ma script.

   2. Locate the following line:

      #MA_OPTIONS="--hauser username --hapassword password 
                   --hapoll 120"
      

   3. Remove the pound sign (#) from the beginning of the line.

   4. Replace username and password with the username and password you established in Step 8 in Configuring the High Availability Service.

      MA_OPTIONS="--hauser gwha --hapassword gwagents --hapoll 120"
      

      The --hapoll switch specifies that the Monitor Agent should check the status of GroupWise agents every 120 seconds. You can use the MA_OPTIONS variable to add any Monitor Agent startup switches to the grpwise-ma script as needed. For information about Monitor Agent startup switches, see Using Monitor Agent Switches in Monitor in the GroupWise 7 Administration Guide.

   5. Save the file, then exit the text editor.

2. Change to the /etc/init.d directory.

3. Stop one of the agents.

4. Check the status of the agent you stopped to make sure it is stopped.

5. Wait for the next Monitor Agent polling cycle.

   You can check and, if necessary, change the Monitor Agent polling cycle in the Monitor Agent Web console. Click Preferences, then scroll down to the HTTP Settings section.

6. After the polling cycle has passed, check the status of the agent again.

   The agent that you stopped should now be running again.

1. Click File > Exit > Yes.

1. Make sure you are logged in as root.

2. Change to the /etc/init.d directory.

3. To stop all of the GroupWise agents installed on the server, enter the following command:

   ./grpwise stop
   

4. To confirm that the agents have stopped, enter the following command:

   ./grpwise status
   

   Agent status is displayed in terms of the names of the domain and post office associated with each agent. It lists the agent locations in the following format:

   POA	[post_office.domain]
   MTA:	[domain]
   Internet Agent:	[domain.GWIA]
   WebAccess:	[WEBAC70A] [gwdva.hostname]

5. Use the following set of commands as needed to stop the agents as daemons and verify their status:

   ./grpwise stop	Stops the GroupWise agents that are installed on the server
   ./grpwise stop agent_location_name	Stops the specified agent
   ./grpwise status	Displays the status of the GroupWise agents that are installed on the server
   ./grpwise status agent_location_name	Displays the status of the specified agent

   IMPORTANT:For convenience in typing the command, the agent_location_name is not case sensitive.

   NOTE:The GroupWise agents are Run Control compliant. During installation, a symbolic link is created from /etc/init.d/grpwise to /usr/sbin/rcgrpwise. Typically, /usr/sbin is already on your path, so you can run rcgrpwise from any directory, rather than changing to /etc/init.d in order to run the grpwise script. A /usr/sbin/grpwise-ma link is also created.

1. Make sure you are logged in as root.

2. Determine the process IDs (PIDs) of the agent to kill:

   POA	ps -eaf | grep gwpoa
   MTA:	ps -eaf | grep gwmta
   Internet Agent:	ps -eaf | grep gwia
   WebAccess:	ps -eaf | grep gwinter
   Monitor:	ps -eaf | grep gwmon

   All of the PIDs for the specified agent are listed.

3. Kill the first process listed for each agent:

   Syntax:

   kill PID
   

   Example:

   kill 1483
   kill 1892
   

   It might take a few seconds for all agent processes to terminate.

4. Repeat the ps commands to verify that the agents have stopped.

1. In the Windows Control Panel, double-click Users and Passwords to add a new user.

2. Grant the user Full Control rights in the domain and post office directories.

1. In the Windows Control Panel, double-click Add/Remove Programs.

2. Click Add/Remove Windows Components.

3. Select Management and Monitoring Tools, click Details, select Simple Network Management Protocol, then click OK

4. Follow the prompts to finish the installation.

For example, on a Windows 2000 server:

1. From the Windows desktop, click Start > Settings > Taskbar & Start Menu > Advanced > Add.

2. Browse to the directory where you installed the GroupWise agent.

   The default installation directories are:

   POA:	c:\grpwise
   MTA:	c:\grpwise
   Internet Agent:	c:\grpwise\gwia
   WebAccess:	c:\webacc
   Monitor:	c:\gwmon

3. Double-click agent executable, then if necessary, add the startup file to the command line.

   POA:	gwpoa.exe @startup_filename.poa
   MTA:	gwmta.exe @startup_filename.mta
   Internet Agent:	gwia.exe @gwia.cfg
   WebAccess:	strtweb.bat
   Monitor:	gwmon.exe

   The startup file for the POA is named after the post office. The startup file for the MTA is named after the domain. The startup file for the Internet Agent is always gwia.cfg. The WebAccess Agent startup file is provided in strtweb.bat. The Monitor Agent does not use a startup file.

4. Click Next.

5. Select the Startup folder, provide a name for the shortcut, then click Finish.

   All programs in the Startup folder are automatically started when the server reboots.

6. If possible, restart the server to verify that the GroupWise agents start automatically.

For example, on a Windows 2000 server:

1. From the Windows desktop, click Start > Settings > Control Panel > Administrative Tools.

2. Double-click Services, select the agent service, then click Start.

   The POA service is named after the post office. The MTA service is named after the domain. The Internet Agent service is named GWIA. The WebAccess Agent service is named WebAccess (webaccess_agent_object_name).

   You can check the status of the agent service by using the Windows Event Viewer. From Administrative Tools, double-click Event Viewer, click Application Log, sort the log entries on the Source column, scroll to the agent service, then double-click a log entry to view information about it.

3. To configure the agent service to start automatically when the server reboots, right-click the agent service, then click Properties.

4. In the Startup Type field, click Automatic, then click OK.

For example, on a Windows 2000 server:

1. From the Windows desktop, click Start > Settings > Control Panel > Administrative Tools.

2. Double-click Services, select the agent service, then click Stop.

   The POA service is named after the post office. The MTA service is named after the domain. The Internet Agent service is named GWIA. The WebAccess Agent service is named WebAccess (webaccess_agent_object_name).