On the Linux server, become root in a terminal window.
If you are installing the WebAccess Agent on a server other than the one where its domain is located, provide access to the domain directory on the server where you are installing the Linux WebAccess Agent.
If the domain directory is located on another Linux server, use your mount command of choice. If the domain is located on a NetWare or Windows server, see Section 19.2.1, Making a NetWare or Windows Server Visible from Linux for suggested mount commands.
As an alternative to a permanent mount, and to provide better performance and stability, you can create a secondary domain and run a Linux MTA on the Linux server local to the WebAccess installation. For instructions, see Creating a New Domain
in Domains
in the GroupWise 7 Administration Guide.
If your Linux environment includes the X Window System, run the GUI GroupWise Installation program to install the Linux WebAccess Agent software, as described in Installing the Linux WebAccess Agent.
or
If the X Window System is not available, run the text-based GroupWise Installation program instead, as described in Installing the GroupWise Agents Using the Text-Based Installation Program.
Configure the WebAccess Agent, as described in Configuring the Linux WebAccess Agent.
On the Gateway Directory page, specify a new name for the WebAccess gateway directory under wpgate in the domain directory, so that the old gateway directory and its contents are retained.
On the Gateway Object page, specify a new object name, so that the old WebAccess Agent object is retained.
In ConsoleOneĀ®, review the property pages for the old WebAccess Agent object and transfer any settings that you have customized on the on the old WebAccess Agent object to the new WebAccess Agent object.
IMPORTANT:The encryption key on the WebAccess Settings page is especially important. Check and transfer it if necessary.
Copy the commgr.cfg file from its location under the new WebAccess gateway directory:
domain_directory/wpgate/new_webaccess_agent_gateway_directory
to the WebAccess, and optionally WebPublisher, software directories:
/opt/novell/groupwise/webaccess /opt/novell/groupwise/webpublisher
If you plan to run multiple WebAccess Agents for the domain, this step needs to be done only for the primary WebAccess Agent, as listed on the Environment property page of the GroupWise Provider object.
Review the existing WebAccess Agent startup file:
old_webaccess_agent_object_name.waa
located on the NetWare or Windows server in:
and transfer any customized settings to the new WebAccess Agent startup file:
new_webaccess_agent_object_name.waa
located on the following directory on the Linux server:
/opt/novell/groupwise/agents/share
Review the old Document Viewer Agent startup file (gwdva.dva) located on the NetWare or Windows server in the same directory with the WebAccess Agent startup file, and transfer any customized settings to the new Document Viewer Agent startup file on the Linux server.
Start the Linux WebAccess Agent with or without a user interface, as described in Starting the Linux WebAccess Agent.
If the WebAccess Agent server console does not appear, or the WebAccess Agent Web console is not available in your Web browser, review the preceding steps to verify that all steps have been followed. For additional assistance, see WebAccess Agent Problems
in Strategies for Agent Problems
in the GroupWise 7 Troubleshooting 2: Solutions to Common Problems.
After the new WebAccess Agent is running successfully, replace the old WebAccess Agent with the new WebAccess Agent in the WebAccess Applicationās provider list.
In ConsoleOne, right-click the GroupWise Provider object, then click
.In the GroupWise WebAccess Agent Information box, click
.Browse to and select the new WebAccess Agent object, then click
to add it to the list of WebAccess Agents.Select the old WebAccess Agent, then click
.Click
to save the updated WebAccess Agent list.Stop the old WebAccess Agent on the NetWare or Windows server.
Delete the old WebAccess Agent object from eDirectory.
Delete the old WebAccess Agent gateway directory under wpgate in the domain directory.
If desired, uninstall the WebAccess Agent software to reclaim disk space on the NetWare or Windows server. See Uninstalling the NetWare GroupWise Agents or Uninstalling the Windows GroupWise Agents.