GroupWise WebAccess includes the enhancements and new features listed below. Changes included in GroupWise 6.5 are indicated by (v6.5). Changes included in GroupWise 6.5 Support Pack 1 are indicated by (v6.5 SP1).
GroupWise 6.5 WebAccess supports Apache Web Server on NetWare 6. Support Pack 1 includes support for Apache 2 Web Server on NetWare 6.5.
The Installation program recognizes the NetWare server's version, installs to the appropriate location (apache directory or apache2 directory), and configures the appropriate files.
For information, see WebAccess System Requirements.
GroupWise 6.5 WebAccess supports the Tomcat 3.3 servlet engine on NetWare 6. Support Pack 1 includes support for the Tomcat 4 servlet engine on NetWare 6.5.
WebAccess does not include the Tomcat servlet engine, but can be installed to a NetWare 6.x server that is using it.
For information, see WebAccess System Requirements.
The Installation program includes a startup switch, -pqa or /pqa, that instructs the program to show only the screens required to create a PQA (Palm Query Application) file. The PQA file can be used on a Palm OS device to access GroupWise through the device.
For more information about the Internet Agent console, see "Creating a PQA File for the WebAccess Client" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The WebAccess Agent includes SSL support to provide secure connections to Post Office Agents (POAs) and the WebAccess Agent Web console. SSL options are configured on the WebAccess Agent object's Network Address page and SSL Settings page in ConsoleOne.
For more information, see "Securing WebAccess Agent Connections Via SSL" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The GroupWise WebAccess Application can be configured to support single sign-on via trusted servers. When enabled, the WebAccess Application authenticates users to GroupWise using authentication header credentials generated by an authentication server (for example, a Novell iChain® Authentication Server).
For information about configuring the WebAccess Application to support single sign-on via trusted servers, see "Configuring the WebAccess Application" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The GroupWise WebAccess Application can be configured to support secure sessions by using session cookies on a per-template-set basis. The session cookie, which is created when the user opens the session, ties the session to the browser and ensures that the WebAccess Application accepts session requests from that browser only. The session cookie is held in memory and exists only as long as the user is logged in.
Session cookie support is configured through the GroupWise WebAccess Application object's Security page in ConsoleOne.
For more information, see "Configuring the WebAccess Application" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The GroupWise WebAccess Application can be configured to enable or disable caching of WebAccess data on proxy servers (or other caching devices) on a per-template-set basis. Proxy servers that cache files can pose an information security risk because any information that the WebAccess Application sends to users is cached. This includes sensitive mailbox information such as message text and passwords.
You can attempt to disable proxy server caching of GroupWise information. If you do so, the WebAccess Application includes a "disable proxy caching" request in the header of each file that it sends. If the proxy server accepts the request, the file is not cached; if it does not accept the request, the file is cached, regardless of this setting.
Proxy server data caching is enabled/disabled through the GroupWise WebAccess Application object's Template page (Define User Interfaces feature) in ConsoleOne.
For more information, see "Configuring the WebAccess Application" in "WebAccess" in the GroupWise 6.5 Administration Guide.
Previous versions of GroupWise WebAccess allowed users to view an attached document or library document in HTML format. If users wanted to open the document in its native application, they had to first save it to their local drives and then open it in the application.
You can now configure WebAccess to enable users to open a document in the document's native application without first saving it to the local drive. This results in a document having two options: View (as HTML) and Open (in native format).
You can enable both options, the View option only, the Open option only, or neither option.You can also enable options for all documents, or you can determine available options based on the type of document. For example, you could force all Microsoft Word documents (.doc files) to use the Open option, while Microsoft Excel documents (.xls files) use the View option.
The Open option requires that 1) the Web browser knows the correct application or plug-in to associate with the document, according to its file extension or MIME type, and 2) the application or plug-in is available to the user. Otherwise, the user is prompted to save the file to disk or specify the application to open it.
The WebAccess viewing and opening options are configured through the GroupWise WebAccess Application object's Setting page. For more information, see "Configuring the WebAccess Application" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The WebPublisher viewing and opening options are configured through the GroupWise WebPublisher Application object's Setting page. For more information, see "Configuring the WebPublisher Application" in "WebAccess" in the GroupWise 6.5 Administration Guide.
With Support Pack 1, you can set a maximum size limit for viewing attachments and library documents in HTML format. If a file exceeds the size limit (1024 KB by default), the file is not rendered to HTML.
The WebAccess viewing options are configured through the GroupWise WebAccess Application object's Setting page. For more information, see "Configuring the WebAccess Application" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The WebPublisher viewing options are configured through the GroupWise WebPublisher Application object's Setting page. For more information, see "Configuring the WebPublisher Application" in "WebAccess" in the GroupWise 6.5 Administration Guide.
GroupWise 6.5 supports disabling of proxy server data caching (see Proxy Server Data Caching (v6.5)). Support Pack 1 adds support for disabling Web browser data caching.
Both proxy server data caching and Web browser data caching are configured through the same option. Therefore, if you disable one, both are disabled.
The location where you enable or disable data caching has changed from the WebAccess Application object's Template page to the Security page.
For more information, see "Configuring the WebAccess Application" in "WebAccess" in the GroupWise 6.5 Administration Guide.
The following features and enhancements have been made to the WebAccess client:
For additional information about WebAccess client features, refer to the WebAccess client Help.
Previous versions of GroupWise WebAccess and WebPublisher allowed users to view an attached document or library document in HTML format. If users wanted to open the document in its native application, they had to first save it to their local drives and then open it in the application.
WebAccess can now be enabled by the administrator to allow users to open a document in the document's native application without first saving it to the local drive. This results in a document having two options: View (as HTML) and Open (in native format).
WebAccess Client Options now include Send Options. Click the Options icon on the toolbar, then click Send Options. You can specify Classification, Priority, Reply Requested, and Return Notification options. These options apply to all items you send.
In an item you are creating, click Send Options. You can specify Classification, Priority, Reply Requested, and Return Notification options. These options apply to the item you are creating.
The Checklist folder is new in both the Windows and WebAccess versions of the GroupWise client.
You can move items to the Checklist folder, arrange items in the order you want, assign due dates to items, and mark them Complete.
The Checklist folder is a system folder. It replaces the Task List folder.
The Sent Items folder displays all the items you have sent that you have not moved to other folders. Use this folder to find items you want to resend, reschedule, retract, and so forth.
The Sent Items folder is a system folder. The Sent Items folder in previous versions of GroupWise was a Find Results folder.
Click the Find icon (a magnifying glass) on the left toolbar of the Main Window to search for items, including document references in your mailbox.
You can do a full-text search or search for text in the subject. You can search in the From or To/CC fields. Select the item types you want to search, the Item Source, and the folders you want to search in, then click Find. The Find Results display, in date descending order, in the right pane of the browser window.
To view basic properties about an item, open an item, then click Properties. To view more detailed properties, open an item, click Properties, then click Other Properties.
You can set the default number of messages to display in the Item List by clicking the Options icon on the toolbar, then clicking General. You can select from 5 to 200 messages to be displayed by default.
If your browser's Print feature prints a message in a format that loses information, click Print View in the Mail Message window to display a printer-friendly version of the message in a new browser window, then print the message from the new window.
If a Web server outage occurs while you are composing a message, your message is not lost when you click Send. It is captured and appears at the bottom of the WebAccess Login page so that you can retrieve it when your Web server comes back up and you log into WebAccess again.