Download
Share
Print this page
  1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. GROUPWISE 7 - WEB ACCESS
  6. Manual

Novell GROUPWISE 7 - WEB ACCESS Manual

Hide thumbs

Advertisement

Quick Links

Download this manual
WebAccess
X I I
Chapter 53, "Scaling Your WebAccess Installation," on page 855
Chapter 54, "Configuring WebAccess Components," on page 869
Chapter 55, "Managing User Access," on page 915
Chapter 56, "Monitoring WebAccess Operations," on page 925
Chapter 57, "Using WebAccess Startup Switches," on page 945
XII
WebAccess
853

Advertisement

loading
Need help?

Need help?

Do you have a question about the GROUPWISE 7 - WEB ACCESS and is the answer not in the manual?

Questions and answers

Related Manuals for Novell GROUPWISE 7 - WEB ACCESS

Summary of Contents for Novell GROUPWISE 7 - WEB ACCESS

  • Page 1 WebAccess X I I Chapter 53, “Scaling Your WebAccess Installation,” on page 855 Chapter 54, “Configuring WebAccess Components,” on page 869 Chapter 55, “Managing User Access,” on page 915 Chapter 56, “Monitoring WebAccess Operations,” on page 925 Chapter 57, “Using WebAccess Startup Switches,” on page 945 WebAccess...
  • Page 2 854 GroupWise 7 Administration Guide...
  • Page 3 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 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 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 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.
  • Page 7 If you’ve already copied the Groupwise WebAccess software to a software distribution directory, run setup.exe from the internet/webacces directory. 2 Click Yes to accept the license agreement and display the Select Components dialog box. 3 Deselect all components except the GroupWise WebAccess application and/or the Groupwise WebPublisher Application, then click Next.
  • Page 8 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 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 on the Web server novell\webaccess\users Windows: Linux: /opt/novell/groupwise/webaccess/users By default, only the GroupWise Provider object and the commgr.cfg file include a WebAccess...
  • Page 10 Redirection/Failover List: Example 1 Assume that the WebAccess Agents are defined as follows: Location WebAccess Agent WebAccess URL No agent defined Post office Agent 1 Domain Agent 4 GroupWise service provider Agent 2 Agent 3 Agent 4 Commgr.cfg Using this information, the WebAccess Application would create the following redirection/failover list: List Entry Taken From...
  • Page 11 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 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 the commgr.cfg file, you can add the WebAccess Agent’s IP address and port number to the URL that calls the WebAccess Application.
  • Page 13 Language Code Language Code German You can add the URL to any Web page. For example, if you are using the Web Services page as your initial WebAccess page, you could add the URL to that page. You should add one URL for each WebAccess Agent.
  • Page 14 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 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 Section 54.1, “Configuring the WebAccess Agent,” on page 870 Section 54.2, “Configuring the WebAccess Application,” on page 879 Section 54.3, “Configuring the Novell Speller Application,” on page 892 Section 54.4, “Configuring the WebPublisher Application,” on page 894 Section 54.5, “Configuring the GroupWise Service Provider,” on page 903 Section 54.6, “Configuring the LDAP Service Provider,”...
  • Page 18 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 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 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 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 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 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: Port Numbers

    3 Configure the SSL settings for the following connections: HTTP: 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. Client/Server: Select from the following options to configure the WebAccess Agent’s use of secure connections to POAs: Disabled: The WebAccess Agent does not support SSL connections.
  • Page 26 3 To change the WebAccess Agent’s IP address, click the Edit button next to the TCP/IP Address field 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.
  • Page 27 54.2 Configuring the WebAccess Application The WebAccess Application, which resides on the Web server, provides the WebAccess user interface. As users perform actions in the WebAccess client, the WebAccess Application passes information between the Web browser and the WebAccess Agent. WebAccess Application Figure 54-4 LDAP...
  • Page 28 3 Modify any of the following fields: 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 webacc.cfg file located in the WebAccess Application’s home directory, which varies by platform.
  • Page 29 The logout URL can be defined in this location and two additional locations. These locations are listed below, in the order that the WebAccess Application checks them. Trusted server logout URL (configured on the Security page) Template-specific logout URL (configured on the Templates page) General logout URL (configured on the Environment page) For example, you define a general logout URL (WebAccess Application object >...
  • Page 30 3 Choose from the following options: 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.5, “Configuring the GroupWise Service Provider,”...
  • Page 31 Java Package: Specify the Java package that contains the template resources used by the WebAccess Application. The default package is com.novell.webaccess.templates. Images URL: Specify the URL for the GroupWise WebAccess image files. These images are merged into the templates along with the GroupWise information. This URL must be relative to the Web server’s document root directory.
  • Page 32 NetWare /com/novell/webaccess/applets Windows: Linux: /gw/com/novell/webaccess/applets Help URL: Specify the URL for the GroupWise WebAccess Help files. This URL must be relative to the Web server’s document root directory. The default relative URL varies by platform. NetWare /com/novell/webaccess/help Windows: Linux: /gw/com/novell/webaccess/help Enable Template Caching: To speed up access to the template files, the WebAccess Application can cache the files to the server’s memory.
  • Page 33 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. Each interface consists of template files that support a specific content type. For example, the predefined Standard HTML interface uses frame-based HTML templates, located in the frames directory, that support the text/html content type.
  • Page 34 Template: This column displays the directory in which the template files are located. Only the directory name is shown. You can append this directory name to the template path shown on the Templates page to see the full template directory path. Content Type: This column displays the content type required by the templates (for example, text/html, text/x-hdml, or text/vnd.wap.wml).
  • Page 35 browser accepts (WebAccess Application object > Browser Accept Types). If no match is made based on the Accept Types information, the WebAccess Application uses the default user interface listed on the User Interfaces tab. Choose from the following options to manage the associations: Add: Click Add to add an entry to the list.
  • Page 36 54.2.4 Securing WebAccess Application Sessions The WebAccess Application includes several settings to help you ensure that user information is secure. You can: Specify a period of time after which inactive sessions are closed. The default is 20 minutes. Secure sessions through the use of client IP binding or browser session cookies. Disable information caching by proxy servers and Web browsers.
  • Page 37 Single Sign-On: The WebAccess Application supports authentication to GroupWise using Base64 authentication header credentials generated by a trusted server (for example, a Novell ® iChain Authentication Server).
  • Page 38 To specify a trusted server whose authentication header credentials are accepted by the WebAccess Application, click Add to display the Add Trusted Server Information dialog box, then provide the server’s IP address or DNS hostname. For more information about the fields in the Add Trusted Server Information dialog box, click the dialog box’s Help button.
  • Page 39 Spell Check Items: Enable this option if you want users to be able to use the Novell Speller to spell check an item’s text before sending the item. Disable this option to remove all Spell Check features from the user interface.
  • Page 40 This setting applies when viewing either library documents or attachments. 4 Click OK. 54.3 Configuring the Novell Speller Application The Novell Speller Application enables users to spell check their messages. The Speller Application is installed automatically with the WebAccess Application. Speller Application...
  • Page 41 2 Click Application > Environment to display the Environment page. 3 Modify any of the following fields: Configuration File: The Speller 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.
  • Page 42 NetWare tomcat_dir\webapps\ROOT\web- inf\classes\com\novell\collexion\morphology\data Windows: Linux: /var/opt/novell/tomcat/webapps/gw/WEB-INF/classes/com/novell/ collexion/morphology/data Maximum Suggestions: Select the maximum number of suggestions the Speller Application returns for misspelled words. The default is 10. Customize Settings in XML: Click this button to launch the XML editor. You can use the editor to add, modify, or delete settings.
  • Page 43 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 file located in the WebPublisher Application’s home directory, which varies by...
  • Page 44 4 Click OK to save the changes. 54.4.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.
  • Page 45 The default installation directory varies by platform. NetWare tomcat_dir\webapps\ROOT\web- inf\classes\com\novell\webpublisher\templates Windows: Linux: /var/opt/tomcat/webapps/gw/WEB-INF/classes/com/novell/ webpublisher/templates Java Package: Specify the Java package that contains the template resources used by the WebPublisher Application. The default package is com.novell.webpublisher.templates. Configuring WebAccess Components 897...
  • Page 46 GroupWise WebPublisher applets, you need to specify the URL for the applets. To mirror the storage location of the GroupWise WebAccess applets, you can store the applets in a com\novell\webpublisher\applets directory under the Web server’s document root directory. The applets URL is then relative to the Web server’s document root directory, which varies by platform.
  • Page 47 Defining WebPublisher User Interfaces 1 From the WebPublisher 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 48 If you do so, this column displays the URL. This URL overrides the logout URL specified on the WebPublisher Application object’s Environment page (see Section 54.3, “Configuring the Novell Speller Application,” on page 892). Choose from the following options to manage the user interfaces: Add: Click Add to add a user interface to the list.
  • Page 49 based on the Accept Types information, the WebPublisher Application uses the default user interface listed on the User Interfaces tab. Choose from the following options to manage the associations: 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. Up: Select an entry from the list, then click Up to move it up in the list.
  • Page 50 Open documents in native format. All users who access WebPublisher through a single Web server have the same feature access. You cannot configure individual user settings. However, if you have multiple Web servers, you can establish different settings for the Web servers by completing the following steps for each server’s WebPublisher Application.
  • Page 51 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 52 WebAccess Agent. By default, the commgr.cfg file is stored in the WebAccess Application’s home directory, which varies by platform. NetWare on the Web server novell\webaccess\users Windows: Linux: /opt/novell/groupwise/webaccess/users In general, you should not need to change this setting. However, if you have multiple WebAccess Agents in your GroupWise system and you are optimizing WebAccess to provide greater scalability and availability, you might need to change the setting.
  • Page 53 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 54 By default, the ldap.cfg file is stored in the WebAccess Application’s home directory, which varies by platform. NetWare on the Web server novell\webaccess\users Windows: Linux: /opt/novell/groupwise/webaccess/users You should avoid changing the location of the file. If you do change the location of the file, you need to make sure to modify the ldap.cfg path in the Java servlet engine’s properties file.

  • Page 55: 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 56 WebAccess Agent. By default, the commgr.cfg file is stored in the WebPublisher Application’s home directory, which varies by platform. NetWare on the Web server novell\webpublisher Windows: Linux: /opt/novell/groupwise/webpublisher In general, you should not need to change this setting. However, if you have multiple WebAccess Agents in your GroupWise system and you are optimizing WebPublisher to provide greater scalability and availability, you might need to change the setting.
  • Page 57 Choose from the following options to manage the WebAccess Agents: Add: Click Add to browse for and select the WebAccess Agent object, then click OK to add it to the list. Edit: Select a WebAccess Agent in the list, then click Edit to edit the WebAccess Agent’s object properties.
  • Page 58 NetWare: sys:\system Linux: /opt/novell/groupwise/agents/share Windows: c:\webacc In the Viewer Agent startup file, you can configure the following aspects of Viewer Agent functioning: Section 54.8.1, “Viewer Agent Web Console,” on page 910 Section 54.8.2, “Document Conversion,” on page 910 Section 54.8.3, “Document Quarantine,” on page 911 Section 54.8.4, “Document Cache,”...
  • Page 59 /lang After editing the Viewer Agent startup file, stop and restart the WebAccess Agent to put the new settings into effect. 54.8.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.
  • Page 60 After editing the Viewer Agent startup file, stop and restart the WebAccess Agent to put the new settings into effect. 54.8.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.
  • Page 61 The following switches configure TCP/IP for the Viewer Agent: /port After editing the Viewer Agent startup file, stop and restart the WebAccess Agent to put the new settings into effect. 54.9 Enabling Web Server Data Compression By enabling data compression on your Web server, you can increase performance for all WebAccess users.
  • Page 62 54.9.2 Apache 2 on Open Enterprise Server (OES) Linux 1 As root, change to the /etc/opt/novell/httpd/conf directory and open the httpd.conf file. 2 Locate the LoadModule entries in the file. 3 Add the following entry: LoadModule deflate_module modules/mod_deflate.so <IfModule mod_deflate.c>...
  • Page 63 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 915 Section 55.2, “Setting the Timeout Interval for Inactive Sessions,” on page 920 Section 55.3, “Configuring User Access to WebAccess Features,” on page 921 Section 55.4, “Customizing the WebAccess Interface,”...
  • Page 64 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 65 Inherit Access: Select this option if you want members of this class of service to inherit their access from the default class of service or another class of service that they have membership Allow Access: Select this option to enable members of the class to use WebAccess. If you select Allow Access, you must also set a timeout interval.
  • Page 66 55.1.3 Adding Users to a Class of Service The following steps help you add users to an existing class of service. For information about adding new classes of service, see Section 55.1.2, “Creating a Class of Service,” on page 916. 1 In ConsoleOne, right-click the WebAccess Agent object, then click Properties.
  • Page 67 Validating the Access Database Validating the Access database checks for physical inconsistencies with the database’s records and indexes. 1 In ConsoleOne, right-click the WebAccess Agent object, then click Properties. 2 Click Access Control > Database Management to display the Database Management page. 3 Click Validate Now.
  • Page 68 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 69 1 In ConsoleOne, right-click the WebAccess Application object, click Properties, then click Application > Security to display the Security page. 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.
  • Page 70 3 Configure the following settings: ® Spell Check Items: Enable this option if you want users to be able to use the Novell Speller to spell check an item’s text before sending the item. Disable this option to remove all Spell Check features from the user interface.
  • Page 71 This option and the View Attachments in HTML Format option can both be enabled at the same time. Doing so gives users both the Open option and the View option, which means they have the choice of opening an attachment in its native application or viewing it as HTML. 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.
  • Page 72 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 73 Section 56.1.1, “Using the WebAccess Agent Server Console,” on page 925 Section 56.1.2, “Using the WebAccess Agent Web Console,” on page 929 Section 56.1.3, “Using Novell Remote Manager,” on page 932 Section 56.1.4, “Using an SNMP Management Console,” on page 932 Section 56.1.5, “Assigning Operators to Receive Warning and Error Messages,”...
  • Page 74 WebAccess Agent 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 75 Logging Box The Logging box displays the logged information. The current log level determines the amount of information that is displayed (see Section , “F10 = Options,” on page 927). 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 76 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 77 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 78 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 79 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 80 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 81 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 82 Admin.WebConsole.enable=true 4 If desired, change the default username and password. A username and password is required. 5 Save the file. 6 Restart Tomcat. NetWare: java -exit tomcat4 Linux: /etc/init.d/novell-tomcat restart Windows: Restart the Tomcat service 934 GroupWise 7 Administration Guide...
  • Page 83 56.2.2 Using the WebAccess Application Web Console 1 In a Web browser, enter the following URL: http://server_address/gw/webacc?action=Admin.Open where server_address is the Web server’s IP address or DNS hostname. 2 When prompted, enter the username and password. The Web console is displayed. 56.3 Monitoring the Document Viewer Agent Like the WebAccess Agent, the Document Viewer Agent has a server console and a Web console Section 56.3.1, “Using the Document Viewer Agent Server Console,”...
  • Page 84 Linux: /opt/novell/groupwise/agents/share Windows: c:\webacc 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 85 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 86 NetWare domain\wpgate\webac70a\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 939 “Modifying WebAccess Agent Log Settings through Startup Switches” on page 940 “Modifying WebAccess Agent Log Settings through the WebAccess Agent Server Console” on...
  • Page 87 Modifying WebAccess Agent Log Settings in ConsoleOne To modify log settings in ConsoleOne: 1 In ConsoleOne, right-click the WebAccess Agent object, then click Properties. 2 Click GroupWise > Log Settings to display the Log Settings page. 3 Modify any of the following properties: Log File Path: By default, this field is empty.
  • Page 88 Modifying WebAccess Agent Log Settings through Startup Switches Startup switches override any log settings you specified through ConsoleOne. See “Modifying WebAccess Agent Log Settings in ConsoleOne” on page 939. For information about startup switches that can be used to modify log settings, see Section 57, “Using WebAccess Startup Switches,”...
  • Page 89 Log Settings property page of their objects in ConsoleOne: WebAccess Application (GroupWiseWebAccess object) WebPublisher Application (GroupWiseWebPublisher object) Novell Speller Application (NovellSpeller object The WebAccess applications log information to log files on disk. You can control the following logging features:...
  • Page 90 The Log Settings pages for the WebAccess Application and the WebPublisher Application are the same. The Log Settings page for the Speller Application does not include some of the fields shown above. 4 Modify any of the following properties: Log File Path: Specify the path to the directory where you want to store the log files. Maximum Log File Age: Specify the number of days you want to retain the log files.
  • Page 91 NetWare: sys:\system\gwdva.dir\log Linux: /var/log/novell/groupwise/gwdva Windows: c:\webacc\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.
  • Page 92 The Document Viewer Agent log files can be viewed through the Document Viewer Web console, as described in “Viewing the Document Viewer Agent Web Console” on page 936. 56.4.5 Interpreting WebAccess Log File Information On startup, the WebAccess records the WebAccess settings currently in effect. Thereafter, it logs events that take place, including errors.
  • Page 93 The location of the startup file varies by platform. NetWare: @webac70a.waa sys:system\gwinter Linux: /opt/novell/groupwise/agents/share/webac70a.waa Windows: c:\webacc\webac70a.waa The startup file is referenced from platform-specific files that are used to start the WebAccess Agent. You can also add startup switches to these platform-specific files.
  • Page 94 WebAccess Agent. For example: NetWare: @webac70a.waa load sys:system\gwinter Linux: @webac70a.waa /opt/novell/groupwise/agents/bin/gwinter Windows: @webac70a.waa c:\webacc\gwinter.exe During installation of the WebAccess Agent, the Installation program creates a default startup file, agent_name.waa, where agent_name is the name assigned to the WebAccess Agent object (for example, webac70a.waa).
  • Page 95 @\\s2\sys\agt\webac70a. gwinter.exe @\\s2\c\agt\weba c70a.waa 57.1.2 /cluster ® Enables the WebAccess Agent to run in a clustered environment (using Novell Cluster Services “Implementing WebAccess in a NetWare Cluster” in “Novell Cluster Services on NetWare” in GroupWise 7 Interoperability Guide.
  • Page 96 57.1.4 /home (Required) Specifies the path to the WebAccess Agent’s gateway directory under the domain directory. If you use the default WebAccess Agent gateway directory name, the path is x:\domain\wpgate\webac70a. This switch is required. NetWare WebAccess Agent Linux WebAccess Agent Windows WebAccess Agent Syntax: /home-[svr\][vol:]\dir...
  • Page 97 --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.com ”webacsvr.provo.novell.co ”webacsvr.provo.novell.co ” m” m” 57.1.10 /log Specifies the path to the log file directory. The default location varies by platform. NetWare: domain\wpgate\webac70a\000.prc Linux: /var/log/novell/groupwise/domain.gateway/000.prc...
  • Page 98 NetWare WebAccess Agent Linux WebAccess Agent Windows WebAccess Agent Example: /log-\agt\log --log /gwsystem/logs /log-\agt\log /log-\\server2\mail:\agt\log /log-m:\agt\log /log-\\server2\mail\agt\log /log-\\server2\c\mail\agt\log Log files are named mmdd.nnn, where mm is the month, dd is the day, and nnn is a sequenced number starting with 001. For example, the first log file used on March 28 is named 0328.001, and the second log file used is named 0328.002.
  • Page 99 Example: /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...
  • Page 100 57.1.17 /port-number Specifies the port number the WebAccess Agent listens to. The default is 7205. See Section 54.1.5, “Changing the WebAccess Agent’s Network Address or Port Numbers,” on page 877. NetWare WebAccess Agent Linux WebAccess Agent Windows WebAccess Agent Syntax: /port-port_number --port port_number /port-port_number...
  • Page 101 The Viewer Agent is configured by editing its startup file (gwdva.dva). The default location for the startup files varies by platform. NetWare: sys:\system Linux: /opt/novell/groupwise/agents/share Windows: c:\webacc The table below summarizes Document Viewer Agent startup switches for all platforms and how they correspond to configuration settings in ConsoleOne.
  • Page 102 NetWare Viewer Agent Linux Viewer Agent Windows Viewer Agent ConsoleOne Settings /logdays --logdays /logdays /loglevel --loglevel /loglevel /logmax --logmax /logmax /maxcache --maxcache /maxcache /maxhold --maxhold /maxhold /maxprobtime --maxprobtime /maxprobtime /maxsize --maxsize /maxsize /maxtime --maxtime /maxtime /maxtrancache --maxtrancache /maxtrancache /maxtrantime --maxtrantime /maxtrantime /maxworkers --maxworkers...
  • Page 103 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.8.3, “Document Quarantine,”...
  • Page 104 NetWare Viewer Agent Linux Viewer Agent Windows Viewer Agent Syntax: /http --http /http See also /httpport, /httppw, and /httpuser. 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”...
  • Page 105 /lang-es 57.2.12 /log 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:\webacc\gwdva.dir\log For more information, see Section 56.4.3, “Controlling Document Viewer Agent Logging,” on page 943.
  • Page 106 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. If you restart the Viewer Agent by restarting the WebAccess Agent on the same day, a new log file is created, named 0518dva.002. See also /loglevel, /logdays, and /logmax.
  • Page 107 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.8.4, “Document Cache,”...
  • Page 108 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.8.5, “Agent Performance,” on page 912. NetWare Viewer Agent Linux Viewer Agent Windows Viewer Agent Syntax:...
  • Page 109 NetWare Viewer Agent Linux Viewer Agent Windows Viewer Agent Example: /maxworkers-20 --maxworkers 40 /maxworkers-60 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.8.5, “Agent Performance,”...
  • Page 110 Sets the path to the directory where the Viewer Agent creates its temporary files. The default varies by platform. See Section 54.8.2, “Document Conversion,” on page 910. NetWare: sys:\system\gwdva.dir\temp Linux: /opt/novell/groupwise/agents/bin/gwdva.dir/temp Windows: c:\webacc\gwdva.dir\temp NetWare Viewer Agent Linux Viewer Agent Windows Viewer Agent Syntax:...

This manual is also suitable for:

Groupwise 7 webaccess