The WebAccess Application, which resides on the web server, provides the GroupWise WebAccess user interface. As users perform actions in GroupWise WebAccess, the WebAccess Application passes information between the web browser, the POA, and the DVA.
During installation, the WebAccess Application is set up with a default configuration in the webacc.cfg file. You can modify the WebAccess Application configuration to meet the needs of your WebAccess users and your administrator preferences.
The location of the webacc.cfg file varies by platform:
|
Linux: |
/var/opt/Novell/groupwise/webaccess |
|
Windows: |
c:\Novell\GroupWise\webaccess |
You can use any ASCII text edit that you prefer to edit the webacc.cfg file.
IMPORTANT:We strongly recommend that you do not modify any settings that are not documented in the following sections.
When you install the WebAccess Application, you configure it to communicate with a single POA. After installation, you can configure the WebAccess Application to communicate with multiple POAs. There is no limit to the number of POAs you can specify. Three POAs is recommended. The POAs you specify must be configured for SOAP.
If the POA that the WebAccess Application is communicating with becomes unavailable, the WebAccess Application contacts the next POA in the list, providing uninterrupted service for WebAccess users.
To specify additional POAs:
Open the webacc.cfg file in a text editor.
Search to find the following lines:
Provider.SOAP.1.ip= Provider.SOAP.1.port=
These lines identify the POA that you specified during installation.
Copy and paste those two lines, replace 1 with 2, and then specify the IP address and SOAP port of a another POA, for example:
Provider.SOAP.2.ip=172.16.5.18 Provider.SOAP.2.port=7191
Repeat Step 3, incrementing the number, and providing the IP addresses and SOAP ports for additional POAs as needed.
Save the webacc.cfg file.
Skip to Putting WebAccess Configuration Changes into Effect.
When you install the WebAccess Application, you configure it to communicate with a single DVA. After installation, you can configure the WebAccess Application to communicate with multiple DVAs. There is no limit to the number of DVAs you can specify. Three DVAs is recommended.
If the DVA that the WebAccess Application is communicating with becomes unavailable, the WebAccess Application contacts the next DVA in the list, providing uninterrupted document conversion for viewing attachments in HTML format.
To specify additional DVAs:
Open the webacc.cfg file in a text editor.
Search to find the following lines:
Provider.DVA.1.ip= Provider.DVA.1.port=
These lines identify the DVA that you specified during installation.
Copy and paste those two lines, replace 1 with 2, and then specify the IP address and SOAP port of a another DVA, for example:
Provider.DVA.2.ip=172.17.5.18 Provider.DVA.2.port=8301
Repeat Step 3, incrementing the number, and providing the IP addresses and SOAP ports for additional DVAs as needed.
Save the webacc.cfg file.
Skip to Putting WebAccess Configuration Changes into Effect.
When viewing attachments using WebAccess, the attachments are cached on your device by default. You can disable caching of viewed attachments in the webacc.cfg file:
In the webacc.cfg file, search for the following lines:
Templates.Interface.1.disableCache: Controls caching of attachments on PCs.
Templates.Interface.2.disableCache: Controls caching of attachments on smart phones.
Templates.Interface.3.disableCache: Controls caching of attachments on tablet devices.
Change false to true for the devices on which you don’t want to cache attachments.
Save the webacc.cfg file.
Continue with Putting WebAccess Configuration Changes into Effect.
By default, the WebAccess Application uses the web browser IP address of the WebAccess user to confirm that, during the same session, it is always communicating with the same user. This is the highest form of security and works well for users on desktop workstations. However, for laptops and mobile devices that are carried to different places, possibly from one network segment to another, this level of security can cause interruptions in user sessions.
Other WebAccess Application security features, such as session cookies, provide excellent security, even without the IP address checking. If you have a large number of mobile WebAccess users, you can turn off the web browser IP address confirmation to make WebAccess more stable for these mobile users.
To disable IP address checking:
Open the webacc.cfg file in a text editor.
Search to find the following line:
Security.UseClientIP.enable=
Change true to false.
Save the webacc.cfg file.
Skip to Putting WebAccess Configuration Changes into Effect.
Some organizations choose to place a single sign-on product such as NetIQ Access Manager between users on the web and the applications they access that are running behind the organization’s firewall. If you use a single sign-on product with WebAccess, you must configure the WebAccess Application to accommodate the single sign-on product.
Open the webacc.cfg file in a text editor.
Search to find the following line:
#Cookie.domain=.novell.com
Remove the pound sign (#) to activate the setting.
Replace .novell.com with the part of your organization’s Internet domain name that is common between the single sign-on product and the web server where the WebAccess Application is installed.
For example, if the Access Manager server is at nam.novell.com and the WebAccess Application is at webacc.novell.com, the domain name used to create cookies would be .novell.com, so that the cookies are accepted by both servers.
Save the webacc.cfg file.
Skip to Putting WebAccess Configuration Changes into Effect.
Every HTTP client like a browser sends an HTTP header called a “User-Agent” string to identify itself. For example, Safari 11 on iPhone with iOS 11 sends: Mozilla/5.0 (iPhone; CPU iPhone OS 11_0 like Mac OS X) AppleWebKit/604.1.38 (KHTML, like Gecko) Version/11.0 Mobile/15A356 Safari/604.1. You can block a particular HTTP client by using information from the HTTP header and adding it to the webacc.cfg file in the UserAgent.deny property. You can add multiple values to this property separated by commas. You can also use wildcard(*) matching to prevent multiple HTTP clients from connecting.
Open the webacc.cfg file in a text editor.
Search to find the following line:
#UserAgent.deny=
Remove the pound sign (#) to activate the setting.
Add the HTTP header information for the client you want to block. For example:
UserAgent.deny=iPhone OS 3_0 like Mac OS X, Ghost Pattern Software, MSIE 7.0
Save the webacc.cfg file.
Continue with Putting WebAccess Configuration Changes into Effect.
Reference these sections to enable WebAccess configuration changes.
By default, the WebAccess Application checks the webacc.cfg file and the gwac.xml file for changes every 10 minutes. When it finds changes, it puts the changes into effect without restarting Tomcat. If you are satisfied with having your changes put into effect within this time interval, no action is required on your part after you edit the webacc.cfg file or the gwac.xml file.
You can change the time interval at which the WebAccess Application checks the webacc.cfg file and the gwac.xml file for changes.
Open the webacc.cfg file in a text editor.
Search to find the following line:
Config.Update.check=10
Change 10 to the number of minutes you want the WebAccess Application to wait before checking for changes to its configuration file.
Save the webacc.cfg file.
You can also manually restart Tomcat in order to put the changes into effect immediately.
|
SLES: |
rcgrpwise-tomcat8 stop
rcgrpwise-tomcat8 start
|
|
Windows: |
|