Page 1 WebAccess X I I Chapter 53, “Scaling Your WebAccess Installation,” on page 877 Chapter 54, “Configuring WebAccess Components,” on page 891 Chapter 55, “Managing User Access,” on page 935 Chapter 56, “Monitoring WebAccess Operations,” on page 945 Chapter 57, “Using WebAccess Startup Switches,” on page 965 WebAccess...
Page 2 876 GroupWise 8 Administration Guide...
Page 3: Webaccess Configurations
Scaling Your WebAccess Installation ® If your GroupWise system is relatively small (one domain and a few post offices) and all post offices reside in the same location, a basic installation of GroupWise WebAccess might very well meet your needs. However, if your GroupWise system is large, spans multiple locations, or requires failover support, you might need to scale your GroupWise WebAccess installation to better meet the reliability, performance, and availability needs of your users.
Page 4: Multiple Webaccess And Webpublisher Applications
Multiple WebAccess Agents Figure 53-2 WebAccess Post Office Agent Post Office Domain WebAccess Post Office Agent Post Office Web Server with Domain WebAccess and WebPublisher Applications WebAccess Post Office Agent Post Office Domain There are various reasons why you might want to add additional WebAccess Agents, including: Improving reliability: One WebAccess Agent might provide sufficient access and performance, but you want to protect against downtime that would occur if the WebAccess Agent became unavailable because of server failure or some other reason.
Page 5 The WebAccess Application and WebPublisher Application Installed to Multiple Web Servers Figure 53-3 Web Server with WebAccess and WebPublisher Applications WebAccess Post Office Agent Post Office Domain Web Server with WebAccess and WebPublisher Applications Some reasons for wanting to use this type of configuration include: Enabling WebAccess users on an intranet to access GroupWise through an internal Web server and WebAccess users on the Internet to access GroupWise through an exposed Web server.
Page 6: Installing Additional Webaccess Components
3 Deselect all components except the GroupWise WebAccess Agent, then click Next. 4 Follow the prompts to create the WebAccess Agent’s gateway directory, install the WebAccess ® Agent software, and create the WebAccess Agent’s object in Novell eDirectory 880 GroupWise 8 Administration Guide...
Page 7: Installing Additional Components On Linux
If you are installing to a domain where another WebAccess Agent already exists, you must use a different directory and object name than the one used for the existing WebAccess Agent. 5 When installation is complete, you need to configure your system so that the WebAccess and WebPublisher Applications know about the WebAccess Agent and can direct the appropriate user requests to it.
Page 8: Configuring Redirection And Failover Support
WebPublisher using an SSL connection. NOTE: The option to install Apache and Tomcat along with the WebAccess Application is not available if you are installing to Novell Open Enterprise Server Linux because Apache and Tomcat are already installed and configured correctly in that environment.
Page 9: How The Webaccess Application Knows Which Webaccess Agents To Use
The GroupWiseProvider object. This is the service provider used by the WebAccess Application to connect to WebAccess Agents. The commgr.cfg file. This file located in the WebAccess Application’s home directory, which varies by platform. NetWare: sys:\Novell\GroupWise\WebAccess on the Web server OES Linux: /var/opt/novell/groupwise/webaccess SLES:...
Page 10 If no other WebAccess Agents are defined (as is the case by default), the WebAccess Application directs all user requests to the WebAccess Agent (Agent 1) listed in the file. This file is commgr.cfg located in the WebAccess Application’s home directory on the Web server. The file commgr.cfg contains the IP address and encryption key for the WebAccess Agent that was associated with the...
Page 11: Synchronizing The Encryption Key
Location WebAccess Agent Agent 2 commgr.cfg Using this information, the WebAccess Application would create the following redirection/failover list: List Entry Taken From Agent 1 GroupWise service provider Agent 2 GroupWise service provider Agent 3 GroupWise service provider Because there is no WebAccess Agent defined in the WebAccess URL, user’s post office, or user’s domain, the WebAccess Application redirects the user’s request to the first WebAccess Agent (Agent 1) in the GroupWise service provider’s list.
Page 12: Specifying A Webaccess Agent In The Webaccess Url
3 Make the encryption key the same as the key for any other WebAccess Agents with which the WebAccess Application communicates. 4 Click OK to save the changes. 53.3.3 Specifying a WebAccess Agent in the WebAccess URL To have the WebAccess Application connect to a WebAccess Agent other than the one specified in file, you can add the WebAccess Agent’s IP address and port number to the URL commgr.cfg that calls the WebAccess Application.
Page 13: Assigning A Default Webaccess Agent To A Post Office
<UL> <LI><A HREF="http://172.16.5.18/gw/ webacc?GWAP.ip=172.16.6.10&GWAP.port=7204>San Francisco </A></LI> <LI><A HREF="http://172.16.5.18/gw/webacc?GWAP.ip=172.16.6.12>New York </A></LI> <LI><A HREF="http://172.16.5.18/gw/ webacc?GWAP.ip=172.16.6.33&GWAP.port=7203>London </A></LI> </UL> The displayed HTML page would contain the following list of locations: San Francisco New York London When a user selects a location, the WebAccess Application routes all requests to the WebAccess Agent at the selected location.
Page 14: Assigning A Default Webaccess Agent To A Domain
3 Select the Override box to turn on the option. 4 In the Default WebAccess Gateway box, browse for and select the WebAccess Agent that you want to assign as the default agent. When you have multiple WebAccess Agents and a user logs in to GroupWise WebAccess, the GroupWise Application running on the Web server checks to see if a default WebAccess Agent has been assigned to the user’s post office.
Page 15: Adding Webaccess Agents To The Groupwise Service Provider's List
3 Select the Override box to turn on the option. 4 In the Default WebAccess Gateway box, browse for and select the WebAccess Agent that you want to assign as the default agent. When you have multiple WebAccess Agents and a user logs in to GroupWise WebAccess, the GroupWise Application running on the Web server checks to see if a default WebAccess Agent has been assigned to the user’s post office, as described in Section 53.3.4, “Assigning a Default...
Page 16 The GroupWise WebAccess Agents list displays the WebAccess Agents the GroupWise service provider can communicate with when attempting to complete a request. By default, the list includes the WebAccess Agent that is defined in the file (listed in the commgr.cfg Configuration File field).
Page 17 Configuring WebAccess Components ® GroupWise WebAccess consists of a number of components. The GroupWise 8 Installation Guide presented a simple overview of those components: WebAccess Components: Simplified Figure 54-1 WebAccess Application Post Office WebAccess Browser Server Agent Library WebPublisher Application Viewer Agent This section of the GroupWise 8 Administration Guide provides additional details about those and...
Page 18: Modifying Webaccess Settings
54.1 Configuring the WebAccess Agent The WebAccess Agent receives user requests from the WebAccess Application and WebPublisher Application, accesses post offices and libraries to process the requests, and then passes information back to the applications. WebAccess Agent Figure 54-3 LDAP Speller Server Application...
Page 19: Modifying Webpublisher Settings
3 Modify any of the following fields: Maximum Threads: This is the maximum number of threads the agent uses at one time to process requests. The default (12) enables the agent to process 12 requests at one time, which is usually sufficient.
Page 20 To add a library to the list, click Add, then browse for and select the library. To change the display name or description for the library, select the library, then click ® Properties. By default, the library’s Novell eDirectory object name is used for the display name.
Page 21: Managing Access To Post Offices
IMPORTANT: When you first set up WebPublisher, library documents are not visible to WebPublisher users until they have been indexed by the POA. You can wait until documents are indexed as part of the POA’s next indexing cycle or you can start the indexing process manually.
Page 22: Automating Reattachment To Netware Servers
4 Define the following properties: Access Mode: The access mode determines whether the WebAccess Agent uses client/server access, direct access, or both client/server and direct access to connect to the post office. With client/server and direct, the WebAccess Agent first tries client/server access; if client/server access fails, it then tries direct access.
Page 23: Securing Webaccess Agent Connections With Ssl
3 Define the following properties: Tree: Specify the eDirectory tree that the WebAccess Agent logs in to. If the WebAccess Agent does not use an eDirectory user account, leave this field blank. Context: Specify the eDirectory context of the WebAccess Agent’s user account. If the WebAccess Agent does not use an eDirectory user account, leave this field blank.
Page 24: Enabling Ssl
2 Click GroupWise > SSL Settings to display the SSL Settings page. 3 Fill in the Certificate File, SSL Key File, and Set Password fields: Certificate File: Select the server certificate file for the WebAccess Agent to use. The certificate file must be in Base64/PEM or PFX format. If you type the filename rather than using the Browse button to select it, use the full path if the file is not in the same directory as the WebAccess Agent program.
Page 25: Changing The Webaccess Agent's Network Address Or Port Numbers
3 In the HTTP field, select Enabled to enable the WebAccess Agent to use a secure connection when passing information to the WebAccess Agent Web console. The Web browser must also be enabled to use SSL; if it is not, a non-secure connection is used. 54.1.5 Changing the WebAccess Agent’s Network Address or Port Numbers If you change the network address (IP address or DNS hostname) of the WebAccess Agent’s server...
Page 26: Binding The Webaccess Agent To A Specific Ip Address
3 To change the WebAccess Agent’s IP address, click the pencil icon to display the Edit Network Address dialog box. 4 Change the IP address or DNS hostname as necessary, then click OK to return to the Network Address page. 5 To change the port numbers used by the WebAccess Agent, type the new port number in the appropriate field.
Page 27: Modifying The Webaccess Application Environment Settings
During installation, the WebAccess Application is set up with a default configuration. However, you can use the information in the following sections to optimize the WebAccess Application configuration: Section 54.2.1, “Modifying the WebAccess Application Environment Settings,” on page 901 Section 54.2.2, “Adding or Removing Service Providers,” on page 903 Section 54.2.3, “Modifying WebAccess Application Template Settings,”...
Page 28 Configuration File: The WebAccess Application does not have access to Novell eDirectory or the GroupWise domain database. Therefore, ConsoleOne writes the application’s configuration information to the file specified in this field. By default, this is the file located in webacc.cfg the WebAccess Application’s home directory, which varies by platform.
Page 29: Adding Or Removing Service Providers
54.2.2 Adding or Removing Service Providers The WebAccess Application receives requests from users and then passes the requests to the appropriate service provider. The service provider fills the requests and returns the required information to the WebAccess Application. The WebAccess Application merges the information into the appropriate template and displays it to the user.
Page 30: Modifying Webaccess Application Template Settings
Add: To add a service provider to the list, click Add, browse for and select the service provider’s object, then click OK. Edit: To edit a service provider’s information, select the provider in the list, then click Edit. For information about the modifications you can make, see Section 54.4, “Configuring the GroupWise Service Provider,”...
Page 31 GroupWise WebAccess. If you create your own templates, you need to place the templates in a new subdirectory in the template base directory. The default template path is based on the Tomcat installation location and varies by platform: NetWare: sys:\tomcat\4\webapps\gw\WEB-INF\classes\templates\webacc OES Linux: /var/opt/novell/tomcat5/ webapps/gw/WEB-INF/classes/templates/webacc SLES: /srv/www/tomcat5/base/ webapps/gw/WEB-INF/classes/templates/webacc Windows: c:\Novell\GroupWise\Tomcat5.5\...
Page 32 Defining WebAccess User Interfaces 1 From the WebAccess Application object’s Templates page, click Define User Interfaces to display the Define User Interfaces dialog box. The dialog box includes three tabs: User Interfaces: The User Interfaces tab lets you add, modify, and remove user interfaces, as well as determine whether or not GroupWise data added to an interface should be cached on proxy servers.
Page 33 The User Interface list displays all available user interfaces. The list includes the following information: User Interface: This column displays the name assigned to the user interface (for example, Standard HTML or Wireless Markup Language). Template: This column displays the directory in which the template files are located. Only the directory name is shown.
Page 34 The Browser User Agents tab lets you associate a user interface with a Web browser. The association is based on the browser’s User Agent information (signature, platform, version, and so forth). For example, if a browser’s User Agent information includes Windows CE (one of the predefined entries), the WebAccess Application uses the Basic HTML interface (no-frames interface).
Page 35: Securing Webaccess Application Sessions
Add: Click Add to add an entry to the list. Edit: Select an entry from the list, then click Edit to edit the entry’s information. Delete: Select an entry from the list, then click Delete to remove the entry. 5 Click OK to save your changes and return to the WebAccess Application object’s Templates page.
Page 36 Inactive sessions are automatically deleted after a period of time. The default path is to the users directory, located in the WebAccess Application’s home directory, which varies by platform. NetWare: on the Web server sys:\Novell\GroupWise\WebAccess\users OES Linux: /var/opt/novell/groupwise/webaccess/users SLES: /var/opt/novell/groupwise/webaccess/users...
Page 37: Controlling Availability Of Webaccess Features
Single Sign-On: The WebAccess Application supports authentication to GroupWise using Base64 authentication header credentials generated by a trusted server (for example, a Novell ® Access Manager Authentication Server).
Page 38 Change their GroupWise mailbox passwords Use Document Management Services Open attachments in native format Open documents in native format View attachments in HTML format View documents in HTML format All users who log in through a single Web server have the same feature access. You cannot configure individual user settings.
Page 39 Open Attachments in Native Format: By default, the Save As option enables users to save message attachments to their local drives and then open them in their native applications. You can turn on this option to enable the Open option. The Open option enables users to open message attachments directly in their native applications without first saving the files to the local drive.
Page 40: Configuring The Webpublisher Application
This option and the Open Documents in Native Format option can both be enabled at the same time. Doing so gives users both the View option and the Open option, which means they have the choice of viewing a document as HTML or opening it in its native application. Exclude Files With These Extensions: If you want to exclude certain file types from having the View option, specify the file types in the Exclude Files With These Extensions field.
Page 41 2 Click Application > Environment to display the Environment page. 3 Modify any of the following fields: Configuration File: The WebPublisher Application does not have access to Novell eDirectory or the GroupWise domain database. Therefore, ConsoleOne writes the application’s configuration information to the file specified in this field. By default, this is the webpub.cfg...
Page 42 54.3.2 Adding or Removing Service Providers The WebPublisher Application receives requests from users and then passes the requests to the appropriate service provider. The service provider fills the requests and returns the required information to the WebPublisher Application. The WebPublisher Application merges the information into the appropriate template and displays it to the user.
Page 43: Modifying Webpublisher Application Template Settings
The default template path is based on the Tomcat installation location and varies by platform: NetWare: sys:\tomcat\4\webapps\gw\WEB-INF\classes\templates\webacc OES Linux: /var/opt/novell/tomcat5/ webapps/gw/WEB-INF/classes/templates/webacc SLES: /srv/www/tomcat5/base/ webapps/gw/WEB-INF/classes/templates/webacc Windows: c:\Novell\GroupWise\Tomcat5.5\...
Page 44 The default relative URL is: tomcat_directory/webapps /gw/com/novell/webpublisher/help Enable Template Caching: To speed up access to the template files, the WebPublisher Application can cache the files to the server’s memory. Select this option to turn on template caching.
Page 45 Browser User Agents: The Browser User Agents tab lets you associate a user interface with a Web browser. The association is based on the browser’s User Agent information (signature, platform, version, and so forth). Browser Accept Types: The Browser Accept Types tab lets you associate a user interface with a Web browser.
Page 46 3 To associate a user interface with a Web browser based on the browser’s User Agent information, click the Browser User Agents tab. The Browser User Agents tab lets you associate a user interface with a Web browser. The association is based on the browser’s User Agent information (signature, platform, version, and so forth).
Page 47: Controlling Availability Of Webpublisher Features
The Browser Accept Types tab lets you associate a user interface with a Web browser. The association is based on the content type the browser accepts. Many browsers accept more than one content type (for example, both text/html and text/plain). If the list contains more than one acceptable content type, the WebPublisher Application uses the browser’s preferred content type, which is the type that is listed first in the browser’s Accept Type header.
Page 48 3 Configure the following settings: Open Documents in Native Format: By default, the Save As option enables user to save library documents to their local drives and then open them in their native applications. You can turn on this option to enable the Open option. The Open option enables users to open documents directly in their native applications without first saving the files to the local drive.
Page 49: Configuring The Groupwise Service Provider
The GroupWise service provider is installed and configured when you install the WebAccess Application to a Web server. The WebAccess installation program creates a Novell eDirectory object for the GroupWise service provider in the same context as the WebAccess Application. The object is named GroupWiseProvider.
Page 50 IP address and the encryption key required by the GroupWise service provider to communicate with the WebAccess Agent. By default, the file is stored in the commgr.cfg WebAccess Application’s home directory, which varies by platform. NetWare: sys:\Novell\GroupWise\WebAccess on the Web server OES Linux: /var/opt/novell/groupwise/webaccess SLES: /var/opt/novell/groupwise/webaccess...
Page 51: Configuring The Ldap Service Provider
Application Service Provider Viewer Agent The GroupWise WebAccess installation program creates a Novell eDirectory object for the LDAP service provider in the same context as the WebAccess Application. The object is named ® LDAPProvider. Using ConsoleOne , you can modify the LDAPProvider object to define the LDAP services that the service provider can contact.
Page 52 ConsoleOne writes the information to the file. ldap.cfg By default, the file is stored in the WebAccess Application’s home directory, which ldap.cfg varies by platform. NetWare: sys:\Novell\GroupWise\WebAccess\users on the Web server OES Linux: /var/opt/novell/groupwise/webaccess/users SLES: /var/opt/novell/groupwise/webaccess/users Windows: on the Web server c:\Novell\GroupWise\WebAccess\users You should avoid changing the location of the file.
Page 53: Configuring The Groupwise Document Service Provider
Service Provider Viewer Agent The WebAccess installation program creates a Novell eDirectory object for the GroupWise Document service provider in the same context as the WebPublisher Application. The object is named GroupWiseDocumentProvider. Using ConsoleOne, you can modify the GroupWiseDocumentProvider object to define the WebAccess Agents that the service provider contacts to fill GroupWise document requests.
Page 54 IP address and the encryption key required by the GroupWise Document service provider to communicate with the WebAccess Agent. By default, the file is stored commgr.cfg in the WebPublisher Application’s home directory, which varies by platform. NetWare: sys:\Novell\GroupWise\WebPublisher on the Web server OES Linux: /var/opt/novell/groupwise/webpublisher SLES: /var/opt/novell/groupwise/webpublisher...
Page 55: Configuring The Document Viewer Agent
Viewer Agent is sufficient to provide basic document conversion functionality. The Viewer Agent is configured by editing its startup file ( ). The default location for the startup files gwdva.dva varies by platform. NetWare: sys:\system Linux: /opt/novell/groupwise/agents/share Windows: c:\Program Files\Novell\GroupWise Server\WebAccess Configuring WebAccess Components 929...
Page 56: Viewer Agent Web Console
In the Viewer Agent startup file, you can configure the following aspects of Viewer Agent functioning: Section 54.7.1, “Viewer Agent Web Console,” on page 930 Section 54.7.2, “Document Conversion,” on page 930 Section 54.7.3, “Document Quarantine,” on page 931 Section 54.7.4, “Document Cache,” on page 931 Section 54.7.5, “Agent Performance,”...
Page 57: Document Quarantine
54.7.3 Document Quarantine You can configure the Viewer Agent to quarantine documents that cannot be converted to HTML so that they can be examined manually if necessary. To enable the file quarantine feature, uncomment the /hold startup switch in the Viewer Agent startup file. Documents that fail HTML conversion are then placed in the subdirectory of the Viewer Agent working directory ( hold...
Page 58: Agent Performance
54.7.5 Agent Performance By default, the Viewer starts 5 worker threads and adds additional threads as needed until reaching 15 threads. If users experience unacceptable delays when trying to view documents, you can increase the number of worker threads so that documents can be processed more quickly. By default, the Viewer Agent has limits on the amount of time it can spend converting a single document and on how large a converted document can become.
Page 59: Enabling Web Server Data Compression
7 Restart Apache. 54.8.2 Apache 2 on Open Enterprise Server (OES) Linux 1 As , change to the directory and open the root /etc/opt/novell/httpd/conf httpd.conf file. 2 Locate the entries in the file. LoadModule 3 Add the following entry:...
Page 60 54.8.3 Apache 2 on SUSE Linux Enterprise Server 9 The steps for Apache 2 on SUSE Linux Enterprise Server 9 are essentially the same as those for Novell Open Enterprise Server, as described in Section 54.8.2, “Apache 2 on Open Enterprise Server (OES) Linux,”...
Page 61: Managing User Access
Managing User Access You can manage various aspects of user experience with the WebAccess client. Section 55.1, “Controlling User Access to Mailboxes,” on page 935 Section 55.2, “Setting the Timeout Interval for Inactive Sessions,” on page 940 Section 55.3, “Configuring User Access to WebAccess Features,” on page 941 Section 55.4, “Customizing the WebAccess Interface,”...
Page 62: Creating A Class Of Service
If a user’s membership in two classes of service is based upon the same level of membership (for example, both through individual user membership), the class that applies is the one that allows the most privileges. For example, if the user belongs to one class of service that allows access to WebAccess and another class that prevents access, the class that allows access applies to the user.
Page 63: Adding Users To A Class Of Service
If you select Allow Access, you must also set a timeout interval. The timeout interval determines how long the WebAccess Agent keeps open a dedicated connection to the post office on behalf of the user. If the agent does not receive a user request within the specified interval, it closes the user’s connection to the post office in order to free up its resources and the Post Office Agent’s resources for other uses.
Page 64: Maintaining The Access Database
3 In the Class of Service list, select the class you want to add members to, then click Add to display the Select GroupWise Object dialog box. 4 Select Domains, Post Offices, Distribution Lists, or Users to display the list you want. 5 In the list, select the domain, post office, distribution list, or user you want, then click Add to add the object as a member in the class.
Page 65 3 Click Validate Now. 4 After the database has been validated, click OK. If inconsistencies are found, see “Recovering the Access Database” on page 939. Recovering the Access Database When you recover the Access database, a new database is created and all salvageable records are copied to the new database.
Page 66: Setting The Timeout Interval For Inactive Sessions
3 Click Recover Now. 4 After the database has been recovered, click OK. 55.2 Setting the Timeout Interval for Inactive Sessions By default, users are logged out of GroupWise WebAccess after 20 minutes if they have not performed any actions that generate requests. Actions such as opening or sending a message generate requests.
Page 67: Configuring User Access To Webaccess Features
2 In the Timeout for Inactive Sessions box, select the number of minutes for the timeout interval. 3 In the Path for Inactive Sessions box, select the path for the directory where you want inactive sessions stored. 4 Click OK. The timeout interval applies to all users who log in through the Web server where the WebAccess Application is running.
Page 68 To configure the WebAccess feature settings: 1 In ConsoleOne, right-click the WebAccess Application object, then click Properties. 2 Click Application > Settings to display the Application Settings page. 3 Configure the following settings: Spell Check Items: Enable this option if you want users to be able to spell check an item’s text before sending the item.
Page 69: Customizing The Webaccess Interface
4 Click OK. 55.4 Customizing the WebAccess Interface GroupWise WebAccess enables you to change the default Novell logo and colors used in the WebAccess interface. For example, you can add your company logo to the main WebAccess window and change the colors to match your company colors.
Page 70 The file is located in the following directory: tomcat_directory/webapps/gw/WEB-INF/classes/templates/webacc 2 If you want to change the logo image: 2a Locate the CUSTOMIZABLE IMAGE FOR GROUPWISE WEBACCESS section at the beginning of the file. 2b To turn on customization for the logo image, set the property to TRUE: WebAccess.Customize.Image.enable WebAccess.Customize.Image.enable=true...
Page 71: Using The Webaccess Agent Server Console
Section 56.1.1, “Using the WebAccess Agent Server Console,” on page 945 Section 56.1.2, “Using the WebAccess Agent Web Console,” on page 949 Section 56.1.3, “Using Novell Remote Manager,” on page 952 Section 56.1.4, “Using an SNMP Management Console,” on page 952 Section 56.1.5, “Assigning Operators to Receive Warning and Error Messages,”...
Page 72 WebAccess Agent Server Console Figure 56-1 The console and its options are described below. Up Time The Up Time field displays how long it has been since the WebAccess Agent was started. Threads The default of 12 threads enables the WebAccess Agent to service 12 user requests at one time. The Busy field displays the number of threads that are currently servicing user requests.
Page 73 Logging Box The Logging box displays the logged information. The current log level determines the amount of information that is displayed (see “F10 = Options” on page 947). For each line, the first item is the number of the thread that processed the user’s request, the second item is the time of the request, and the third item is the information associated with the request.
Page 74 Linux WebAccess Agent Server Console Figure 56-2 Windows: Using the WebAccess Agent Server Console The Windows WebAccess Agent server console lets you monitor the operation of the agent. The server console, shown below, is displayed in a DOS window. Windows WebAccess Agent Server Console Figure 56-3 The console and its options are described below.
Page 75: Using The Webaccess Agent Web Console
F1 or F7 Shuts down and exits the agent. Cycles the logging level among Normal, Verbose, and Diagnostic. Normal displays initial statistics, user logins, warnings, and errors; Verbose displays Normal logging plus user requests; and Diagnostic displays Verbose logging plus thread information. The default is Normal logging. Use Verbose only if you are troubleshooting a problem with WebAccess.
Page 76 You cannot use the Web console to change any of the WebAccess Agent’s settings. Changes must be made through ConsoleOne, the WebAccess Agent console, or the startup file. Refer to the following sections for information about enabling and using the Web console: “Enabling the WebAccess Agent Web Console”...
Page 77 5 In the HTTP User Name field, enter an arbitrary username (for example, webcon). 6 Click Set Password to assign a password (for example, monitor). 7 Click OK to save your changes. Viewing the WebAccess Agent Web Console 1 In a Web browser, enter the following: http://IP_address:agent_port https://IP_address:agent_port where IP_address is the IP address of the server where the WebAccess Agent is running, and...
Page 78: Using Novell Remote Manager
56.1.3 Using Novell Remote Manager If the WebAccess Agent is running on NetWare 6.5 or on Novell Open Enterprise Server (OES), you can use the IP Address Management feature in Novell Remote Manager (Manage Server > IP Address Management) to view the IP address and port configuration for the WebAccess Agent. This is also true for other GroupWise agents (MTA, POA, and Internet Agent) running on NetWare 6.5/...
Page 79 To assign an operator: 1 In ConsoleOne, right-click the WebAccess Agent object, then click Properties. 2 Click GroupWise > Gateway Administrators to display the Gateway Administrators page. 3 Click Add, select a user, then click OK to add the user to the Gateway Administrators list. 4 Make sure Operator is selected as the Administrator Role.
Page 80: Monitoring The Webaccess Application
Section 56.2.2, “Using the WebAccess Application Web Console,” on page 955 56.2.1 Enabling the WebAccess Application Web Console 1 Edit the file, located in the WebAccess Application’s home directory, which webacc.cfg varies by platform. NetWare: sys:\Novell\GroupWise\WebAccess on the Web server OES Linux: /var/opt/novell/groupwise/webaccess SLES: /var/opt/novell/groupwise/webaccess Windows:...
Page 81: Using The Webaccess Application Web Console
6 Restart Tomcat. NetWare: unload java load tomcat4 Linux: Novell Open Enterprise Server 2 Linux installation of Apache: /etc/init.d/novell-tomcat5 stop /etc/init.d/novell-tomcat5 start SUSE Linux Enterprise Server 10 installation of Apache: /etc/init.d/tomcat5 stop /etc/init.d/tomcat5 start Windows 1. At the Windows server, click Start > Administrative Tools > Services.
Page 82: Using The Document Viewer Agent Web Console
Linux: /opt/novell/groupwise/agents/share Windows: c:\Program Files\Novell\GroupWise Server\WebAccess 2 Scroll down to the HTTP monitoring section. 3 Remove the comment character (;) from the /http startup switch to enable HTTP for the Document Viewer Agent. 4 If the default HTTP port of 7439 is already in use on the server, remove the comment marker from the /httpport switch and provide a unique port number.
Page 83: Using Webaccess Log Files
The Web console is displayed. Through the Web console you can view the following information: Status: Displays how long the Document Viewer Agent has been up, the number of worker threads it has started, the current server utilization, and statistics about the files the worker threads have processed.
Page 84: Controlling Webaccess Agent Logging
Section 56.4.2, “Controlling WebAccess Application Logging,” on page 961 Section 56.4.3, “Controlling Document Viewer Agent Logging,” on page 963 Section 56.4.4, “Viewing WebAccess Log Files,” on page 964 Section 56.4.5, “Interpreting WebAccess Log File Information,” on page 964 56.4.1 Controlling WebAccess Agent Logging The WebAccess Agent provides logging options to help you monitor the operation of the agent.
Page 85 NetWare and domain\wpgate\webac80a\000.prc Windows: Linux: /var/log/novell/groupwise/domain_name.gateway_name/000.prc For information about modifying log settings, see the following sections: “Modifying WebAccess Agent Log Settings in ConsoleOne” on page 959 “Modifying WebAccess Agent Log Settings through Startup Switches” on page 960 “Modifying WebAccess Agent Log Settings through the WebAccess Agent Server Console” on...
Page 86 Logging Level: There are four logging levels: Off, Normal, Verbose, and Diagnostic. Off turns logging off; Normal displays initial statistics, user logins, warnings, and errors; Verbose displays normal logging plus user requests; and Diagnostic displays Verbose logging plus thread information. The default is Normal logging. Use Diagnostic only if you are troubleshooting a problem with WebAccess.
Page 87: Controlling Webaccess Application Logging
Modifying Log Settings through the Windows WebAccess Agent Server Console You can use the Windows WebAccess Agent’s console to modify the logging level. All other log settings must be modified through ConsoleOne or startup switches. See “Modifying WebAccess Agent Log Settings in ConsoleOne” on page 959 “Modifying WebAccess Agent Log Settings through Startup Switches”...
Page 88 NetWare: on the Web server sys:\Novell\GroupWise\WebAccess\logs OES Linux: /var/opt/novell/groupwise/webaccess/logs SLES: /var/opt/novell/groupwise/webaccess/logs Windows: c:\Novell\GroupWise\WebAccess\logs on the Web server To modify the application log settings: 1 In ConsoleOne, browse to and select the Domain object where the application object is located. 2 Right-click the application object (GroupWiseWebAccess, or GroupWiseWebPublisher), then click Properties.
Page 89: Controlling Document Viewer Agent Logging
Linux: /var/log/novell/groupwise/gwdva Windows: c:\Program Files\Novell\GroupWise Server\WebAccess\gwdva.dir\log Because the Document Viewer Agent is currently configured using switches in its startup file, you must activate the switches in order to change how logging is performed. 1 Use an ASCII text editor to edit the Document Viewer Agent startup file ( gwdva.dva...
Page 90: Viewing Webaccess Log Files
56.4.4 Viewing WebAccess Log Files You can view the log file for the current WebAccess Agent session, or you can view archived log files. The current WebAccess Agent log file is viewable through the NetWare WebAccess Agent console, as described in “NetWare: Using the WebAccess Agent Server Console”...
Page 91: Using Webaccess Startup Switches
NetWare: sys:\system Linux: /opt/novell/groupwise/agents/share/ Windows: c:\Program Files\Novell\GroupWise Server\WebAccess The table below summarizes WebAccess Agent startup switches for all platforms and how they correspond to configuration settings in ConsoleOne. Switch starts with: a b d e f g s t u...
Page 92: File Name
NetWare: load sys:system\gwinter @webac80a.waa Linux: /opt/novell/groupwise/agents/bin/gwinter @webac80a.waa Windows: c:\Program Files\Novell\GroupWise Server\WebAccess\gwinter.exe @webac80a.waa During installation of the WebAccess Agent, the Installation program creates a default startup file, , where agent_name is the name assigned to the WebAccess Agent object (for agent_name.waa example, ).
Page 93 GroupWise 8 Interoperability Guide. ® If you are running the NetWare WebAccess Agent on the latest version of NetWare 6.5/OES NetWare and Novell Cluster Services, the WebAccess Agent can detect the cluster automatically. NetWare WebAccess Linux WebAccess Agent Windows WebAccess Agent Agent...
Page 94: Http Port
NetWare WebAccess Agent Linux WebAccess Agent Windows WebAccess Agent Syntax: /home-[svr\][vol:]\dir --home /dir /home-[drive:]\dir /home-\\svr\vol\dir /home-\\svr\sharename\dir Example: /home-\provo1 --home /gwsystem/provo1 /home-\provo1 /home-mail:\provo1 /home-m:\provo1 /home-server2\mail:\provo1 /home-\\server2\c\provo1 /home-\\server2\mail\provo1 57.1.5 /http If the WebAccess Agent’s Web console is disabled in ConsoleOne, this switch enables the Web console.
Page 95 --ip IP_address /ip-IP_address /ip-”full_DNS_name” --ip ”full_DNS_name” /ip-”full_DNS_name” Example: /ip-172.16.5.18 --ip 172.16.5.18 /ip-172.16.5.18 /ip- --ip /ip- ”webacsvr.provo.novell.co ”webacsvr.provo.novell.co ”webacsvr.provo.novell.co m” m” m” 57.1.10 /log Specifies the path to the log file directory. The default location varies by platform. NetWare and domain\wpgate\webac80a\000.prc Windows: Linux: /var/log/novell/groupwise/domain.gateway/000.prc...
Page 96 See also /logdays, /logdiskon, /loglevel, and /logmax 57.1.11 /logdays Specifies the maximum number of days to keep log files. This setting works in combination with the /logmax setting. Log files are deleted when the maximum number of days or disk space size is reached, whichever comes first.
Page 97: Port Number
/maxusers-300 --maxusers 400 /maxusers-500 57.1.16 /password Used by the NetWare WebAccess Agent only. Specifies the Novell eDirectory password to use to access the network servers where the GroupWise domain directory and post office directories reside. NetWare WebAccess Agent Linux WebAccess Agent Windows WebAccess Agent...
Page 98 NetWare WebAccess Agent Linux WebAccess Agent Windows WebAccess Agent Syntax: /port-port_number --port port_number /port-port_number Example: /port-1678 --port 1679 /port-1680 See also /ip. 57.1.18 --show Used by the Linux WebAccess Agent only. Running the WebAccess Agent with this option disabled (the default) causes the WebAccess Agent to run as a daemon without a user interface. Enabling this option causes the logging UI to appear in a terminal window.
Page 99: Document Viewer Agent Startup Switches
NetWare: sys:\system Linux: /opt/novell/groupwise/agents/share Windows: c:\Program Files\Novell\GroupWise Server\WebAccess The table below summarizes Document Viewer Agent startup switches for all platforms and how they correspond to configuration settings in ConsoleOne. Switch starts with: c d e u v w x y z...
Page 100 NetWare Viewer Agent Linux Viewer Agent Windows Viewer Agent ConsoleOne Settings /maxcache --maxcache /maxcache /maxhold --maxhold /maxhold /maxprobtime --maxprobtime /maxprobtime /maxsize --maxsize /maxsize /maxtime --maxtime /maxtime /maxtrancache --maxtrancache /maxtrancache /maxtrantime --maxtrantime /maxtrantime /maxworkers --maxworkers /maxworkers /minworkers --minworkers /minworkers /port --port /port /relay --relay...
Page 101 Syntax: /domain-domain_name --domain domain_name /domain-domain_name Example: /domain-corporate.com --domain novell.com /domain-suse.com See also /hold, /maxhold, /email, and /relay. 57.2.4 /email Provides the e-mail address of a user that the Viewer Agent should notify when it places a document in quarantine. See Section 54.7.3, “Document Quarantine,”...
Page 102 57.2.7 /httpport Sets the HTTP port number used for the Viewer Agent to communicate with the WebAccess Agent. The default is 7439; the setting must be unique. See “Enabling the Document Viewer Agent Web Console” on page 956. NetWare Viewer Agent Linux Viewer Agent Windows Viewer Agent Syntax:...
Page 103 Sets the directory where the Viewer Agent stores its log files. The default location varies by platform. NetWare: sys:\system\gwdva.dir\log Linux: /var/log/novell/groupwise/gwdva Windows: c:\Program Files\Novell\GroupWise Server\WebAccess\gwdva.dir\log For more information, see Section 56.4.3, “Controlling Document Viewer Agent Logging,” on page 963. NetWare Viewer Agent Linux Viewer Agent...
Page 104 Typically you find multiple log files in the specified directory. The first 4 characters represent the date. The next 3 characters identify the agent. A three-digit extension allows for multiple log files created on the same day. For example, a log file named 0518dva.001 indicates that it is a Viewer Agent log file, created on May 18.
Page 105 57.2.16 /maxcache Specifies in megabytes the maximum amount of disk space that the library cache can occupy. The default is 100. To clear out the contents of the library cache, set /maxcache to 0 (zero); this also disables the library cache in the future. See Section 54.7.4, “Document Cache,”...
Page 106 See also /maxtime. 57.2.20 /maxtime Specifies in seconds the maximum amount of time a worker thread can work on a converting a single document. The default is 120 (2 minutes). Section 54.7.5, “Agent Performance,” on page 932. NetWare Viewer Agent Linux Viewer Agent Windows Viewer Agent Syntax:...
Page 107 NetWare Viewer Agent Linux Viewer Agent Windows Viewer Agent Example: /maxworkers-6 --maxworkers 7 /maxworkers-8 See also /minworkers. 57.2.24 /minworkers Specifies the minimum number of worker threads that the Viewer Agent starts. The default is 5. The maximum number of threads is limited only by available memory resources on the server. See Section 54.7.5, “Agent Performance,”...
Page 108 Sets the path to the directory where the Viewer Agent creates its temporary files. The default varies by platform. See Section 54.7.2, “Document Conversion,” on page 930. NetWare: sys:\system\gwdva.dir\temp Linux: /opt/novell/groupwise/agents/bin/gwdva.dir/temp Windows: c:\Program Files\Novell\GroupWise Server\WebAccess\gwdva.dir\temp NetWare Viewer Agent Linux Viewer Agent Windows Viewer Agent Syntax: /temp-[svr\][vol:]\dir --temp /dir /temp-[drive:]\dir /temp-\\svr\vol\dir...

This manual is also suitable for:

Groupwise 8

Novell GROUPWISE 8 - WEBACCESS Manual

Quick Links

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Novell GROUPWISE 8 - WEBACCESS

Summary of Contents for Novell GROUPWISE 8 - WEBACCESS

This manual is also suitable for:

Table of Contents