Additional WebAccess files are integrated into your Web server to support the WebAccess client and the WebAccess Agent Web console. See Apache/Tomcat Installation. See also WebAccess Agent Queue Directory.
On a NetWare server, the GroupWise WebAccess Agent is typically installed in the sys:\system directory. You can choose a different location during installation.
The gwenn4.nlm file is the GroupWise 6.x Agent Engine, a program that is shared by all GroupWise agents. It provides the following services to the agents:
The first agent loaded on a server automatically loads the GroupWise Agent Engine.
The strtweb.ncf file is the NetWare configuration file that automatically loads the WebAccess Agent whenever the server is restarted. A typical strtweb.ncf file would look similar to the following:
load sys:\system\gwinter @webac65a.waa
It includes the WebAccess Agent startup file in the load command. For more information, see "Starting GroupWise WebAccess" in "Installing GroupWise WebAccess" in the GroupWise 6.5 Installation Guide.
The WebAccess Agent startup file contains startup switches for the WebAccess Agent. Switch settings placed in the WebAccess Agent startup file override comparable options set for the WebAccess Agent in ConsoleOne. The startup file is named the same as the WebAccess Agent object in ConsoleOne. The default is webac65a.
During installation, a customized version of the WebAccess Agent startup file is created. This customized version has the /home startup switch automatically set to the domain directory where the WebAccess Agent's queue directories are located. See "Using WebAccess Agent Startup Switches" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The x*10.nlm programs provide XIS capability for the GroupWise agents, so that you can create XML documents to monitor and change the agents as needed.
The gwinter.xml file is a specialized WebAccess Agent configuration file for use in the XIS environment.
The cache\template\xx directory holds language-specific HTML template files for viewing documents in WebAccess and WebPublisher. The xx is a two-letter language code.
You can change the location of the cache directory, as described in "Modifying WebPublisher Settings" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The help directory holds help files and images used by the WebAccess Agent Web console. See "Monitoring the WebAccess Agent through the Web Console" in "WebAccess" in the GroupWise 6.5 Administration Guide.
Novell GroupWise installation directory |
|
Linux agent installation directory |
|
Subdirectory for GroupWise agent executables |
|
Subdirectory for GroupWise agent library files |
|
Subdirectory for icon images |
|
Subdirectory for agent shared files |
|
Subdirectory for agent Web console files |
|
Subdirectory for WebAccess Application files |
|
webacc.cfg |
WebAccess Application configuration file |
Subdirectory for WebAccess Application files |
|
WebPublisher Application configuration file |
|
Subdirectory for HTML template files |
Additional WebAccess files are integrated into your Web server to support the WebAccess client and the WebAccess Agent Web console. See Apache/Tomcat Installation. See also WebAccess Agent Queue Directory.
On a Linux server, the WebAccess Agent is always installed in subdirectories of /opt/novell/groupwise/agents.
The bin directory holds GroupWise executable files.
The gwinter file is the WebAccess Agent executable. You run this executable file to start the WebAccess Agent. See "Setting Up GroupWise WebAccess on Linux" in "Installing GroupWise WebAccess" in the GroupWise 6.5 Installation Guide.
The gwinter.xml file is a specialized configuration file for use in the XIS environment.
The webac6axx.waa file is the boilerplate file from which a domain-specific webac65a.waa file is created in the share directory. The webac65a represents the name of the WebAccess Agent object in eDirectory. The xx represents a two-letter language code.
The lib directory holds GroupWise shared library files.
The share directory holds agent startup files and files that are used by the agent consoles and Web consoles.
The WebAccess Agent startup file contains startup switches for the WebAccess Agent. Switch settings placed in the WebAccess Agent startup file override comparable options set for the WebAccess Agent in ConsoleOne. The startup file is named the same as the WebAccess Agent object in ConsoleOne. The default is webac65a.
During installation, a customized version of the WebAccess Agent startup file is created. This customized version has the /home startup switch automatically set to the domain directory where the WebAccess Agent's queue directories are located. See "Using WebAccess Agent Startup Switches" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The webaccess directory holds files used by the WebAccess Application.
The webacc.cfg file holds the same configuration information that is stored on the WebAccess Application object (named GroupWiseWebAccess) in eDirectory. For more information, see "Configuring the WebAccess Application" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The commgr.cfg file holds the same configuration information that is stored on the GroupWise Provider object (named GroupWiseProvider) in eDirectory, including the IP address and encryption key for the WebAccess Agent. This information enables the WebAccess Application to communicate with the WebAccess Agent. For more information, see "Configuring the GroupWise Service Provider" in "WebAccess" in the GroupWise 6.5 Administration Guide.
A copy of the commgr.cfg file is automatically maintained in the WebAccess Agent queue directory (domain/wpgate/webac65a).
The spellchk.cfg file holds the same configuration information that is stored on the Novell Speller Application object (named NovellSpeller) in eDirectory. For more information, see "Configuring the Novell Speller Application" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The ldap.cfg file holds the same configuration information that is stored on the LDAP Provider object (named LDAPProvider) in eDirectory. For more information, see "Configuring the LDAP Service Provider" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The logs subdirectory holds WebAccess Application log files. For more information, see "Controlling WebAccess Application Logging" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The users subdirectory holds session files for WebAccess users. If WebAccess times out after a period of user inactivity, the user's session information is saved. When the user logs back in, the session information is retrieved so that the user can continue working without loss of data. Also, users' message text is saved during each session, so that if the WebAccess Application is restarted or goes down, users do not lose the message text they were composing at the time. Session files are deleted when users log back in.
The webpublisher directory holds files used by the WebPublisher Application.
The webpub.cfg file holds the same configuration information that is stored on the WebPublisher Application object (named GroupWiseWebPublisher) in eDirectory. For more information, see "Configuring the WebPublisher Application" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The commgr.cfg file holds the same configuration information that is stored on the GroupWise Provider object (named GroupWiseProvider) in eDirectory, including the IP address, port number, number of threads, and encryption key for the WebAccess Agent. This information enables the WebAccess Application to communicate with the WebAccess Agent. For more information, see "Configuring the GroupWise Service Provider" in "WebAccess" in the GroupWise 6.5 Administration Guide.
A copy of the commgr.cfg file is automatically maintained in the WebAccess Agent queue directory (domain/wpgate/webac65a).
The default directory holds boilerplate versions of the webpub.cfg and commgr.cfg files.
The logs subdirectory holds WebPublisher Application log files. For more information, see "Controlling WebPublisher Application Logging" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The cache\template\xx directory holds language-specific HTML template files for viewing documents in WebAccess and WebPublisher. The xx is a two-letter language code.
You can change the location of the cache directory, as described in "Modifying WebPublisher Settings" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The /etc/init.d directory is the standard location for Linux startup scripts.
The grpwise-wa script is created automatically during installation. You can use the script to start, restart, stop, and display status information about the WebAccess Agent. For more information about starting the WebAccess Agent, see "Setting Up GroupWise WebAccess on Linux" in "Installing GroupWise WebAccess" in the GroupWise 6.5 Installation Guide.
The rc3.d directory holds symbolic links to scripts that you want your Linux server to run when it is booted to run level 3 (multi-user; boots to a text mode login prompt without The X Window System). The symbolic link to the grpwise-wa script is S99grpwise-wa. It is created if you choose during installation to have the WebAccess Agent start automatically when the server boots.
The rc5.d directory holds symbolic links to scripts that you want your Linux server to run when it is booted to run level 5 (multi-user; boots to The X Window System login dialog box). The symbolic link to the grpwise-wa script is S99grpwise-wa. It is created if you choose during installation to have the WebAccess Agent start automatically when the server boots.
The /var/log directory is the standard location for log files on Linux. All GroupWise agent log files are created in the novell/groupwise subdirectory.
The domain.webac65a directory is a domain-specific location for WebAccess Agent log files.
Within the 000.prc directory, the WebAccess Agent creates log files (mmddweb.nnn) to inform you of its processing and any problems it encounters. For more information about log files, see "Controlling WebAccess Agent Logging" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The first two digits of the filename represent the month; the next two digits represent the day of the month. The three-digit extension is a sequence number for multiple log files created on the same day. For example, 0518web.002 is the second WebAccess Agent log file created on May 18.
Additional WebAccess files are integrated into your Web server to support the WebAccess client and the WebAccess Agent Web console. See Apache/Tomcat Installation. See also WebAccess Agent Queue Directory.
On a Windows server, the WebAccess Agent can be installed in any directory you choose. The default location is c:\webacc. The WebAccess Agent desktop icon is set up to include the full path to whatever directory you choose.
The gwenv1a.dll file is the GroupWise Agent Engine, a program that is shared by all GroupWise agents. It provides the following services to the agents:
The first agent started on a server automatically starts the GroupWise Agent Engine DLL.
The strtweb.bat file is used to start the WebAccess Agent. The batch file specifies the WebAccess startup file. A typical strtweb.bat file includes the following:
title Novell GroupWise WebAccess
@echo off
cls
gwinter.exe @webac65a.waa
You run this batch file to start the WebAccess Agent. See "Starting GroupWise WebAccess" in "Installing GroupWise WebAccess" in the GroupWise 6.5 Installation Guide.
The WebAccess Agent startup file contains startup switches for the WebAccess Agent. Switch settings placed in the WebAccess Agent startup file override comparable configuration options set for the WebAccess Agent in ConsoleOne. The startup file is named the same as the WebAccess Agent object in eDirectory. The default is webac65a.
During installation, the WebAccess Agent startup file is created with the /home startup switch automatically set to the domain directory where the WebAccess Agent queue directory (domain\wpgate\webac65a) is located. See "Using WebAccess Agent Startup Switches" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The gwwanxx.dll files contain all language-specific information for the WebAccess Agent. The digit n is a version number. The last two characters xx are a language code.
The gwwasnmp.dll file provides interaction with the Windows SNMP Service, so that you can monitor the WebAccess Agent using an SNMP monitoring program. This file is not installed unless you enable SNMP during installation. It cannot be installed if the SNMP Service is not installed on the Windows server.
The x*10.dll programs provide XIS capability for the GroupWise agents, so that you can create XML documents to monitor and change the agents as needed.
The gwia.xml file is a specialized agent configuration file for use in the XIS environment.
The cache\template\xx directory holds language-specific HTML template files for viewing documents in WebAccess and WebPublisher. The xx is a two-letter language code.
You can change the location of the cache directory, as described in "Modifying WebPublisher Settings" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The help directory holds help files and images used by the WebAccess Agent Web console. See "Monitoring the WebAccess Agent through the Web Console" in "WebAccess" in the GroupWise 6.5 Administration Guide.