Loading the GroupWise WebAccess Agent and Application


This section discusses how to start the WebAccess Agent and WebAccess Application. The WebAccess Agent is one process and the WebAccess Application is two processes.

Loading the GroupWise WebAccess Agent

On NetWare, load the GroupWise WebAccess Agent by typing STRTWEB, which calls the STRTWEB.NCF file. You should also consider adding load commands to the server's AUTOEXEC.NCF file.

Tip

If you installed your WebAccess Agent files to a directory other than SYS:\SYSTEM, the STRTWEB.NCF file does not pick up this path when it loads GWINTER. You will need to modify the STRTWEB.NCF file to include the correct path to the GWINTER.NLM file.


For Windows servers, follow these steps: For Windows 200x, a shortcut called GroupWise WebAccess has been created for you, or the Agent has been configured as a service if you chose that installation option. Generally the shortcut is available under Start, Programs, Novell GroupWise WebAccess. A batch file called STRTWEB.BAT is created, and is installed in the C:\WEBACC directory by default. If the Agent has been installed as a service, you must start and stop the WebAccess Agent via the Windows Services found in Control Panel, Administrative Tools, Services.

Here's an explanation of what's in the STRTWEB.NCF file on a NetWare server. Following is a sample STRTWEB.NCF file:

Load SYS:system\gwinter @WEBAC70A.waa

When you load the WebAccess Agent, take notice that GWINTER.NLM auto-loads several other NLMs, starting with SC*.NLM, and several instances of GWDVA.NLM. As soon as a user views an attachment, one or more VS*.NLMs will be loaded as well. These NLMs are used when a user views an attachment that might be some sort of document type from the WebAccess client. The VS*.NLMs take very little server memory because only a small piece of them loads when you load the Agent. When a user needs to actually view a document, the entire viewer NLM loads at that point.

Note

On NetWare, the Viewer Agent requires at least 1GB of memory for running about five worker processes.

On NetWare, you must install the latest Support Pack for your version of NetWare in order to have the correct version of clib.nlm.

On NetWare, Memory Protection Fault Cleanup must be set to On for the Viewer Agent worker processes to recover successfully when a document fails HTML conversion.

On NetWare, when a document fails HTML conversion and its worker process dies, NetWare creates a small file named core*.dmp in the server's root directory. You should periodically delete these files.


The install also creates a STOPWEB.NCF file, which will shut down the WebAccess Agent. It simply contains the line UNLOAD GWINTER, which will unload the WebAccess Agent.

Following are some useful switches that can be used in strtweb.ncf or strtweb.bat (if you want to modify the startup file):

  • @filename: This switch allows you to place all startup switches in a particular file. This is similar to when a domain or post office agent is loaded. This switch is not used by default.

  • /help: If the GWINTER.NLM or GWINTER.EXE files are loaded with the /help switch, all startup switches are displayed with brief descriptions.

  • /maxusers-: Enter the maximum number of concurrent users that the Agent will support. The default is 250 users.

  • /user-: Enter any username here. The username is not actually used in most customer environments; the WebAccess Agent just requires that the switch be filled in.

  • /password-: Enter the password for the user defined in the /user- switch. The password does not actually need to be accurate in most customer environments.

  • /ip-: Enter the IP address that the Agent will bind to. The Agent will bind to the first bound IP address of the server by default.

Note

When you install the WebAccess Agent, it will create a startup file. This startup file is the name of the WebAccess Agent that you defined during the install (by default, WEBAC70A.WAA).

An example of a 7.0 STRTWEB.NCF file is load sys:system\gwinter @WEBAC70A.waa.

The WEBAC70A.WAA file contains most of the startup switches you might use on the WebAccess Agent, just like the message transfer agent (MTA) and POA startup files do. A sample WebAccess Agent startup file can be found at the following location: GroupWise 7 SDD\INTERNET\WEBACCES\config\AgentConfig.waa.


Loading the GroupWise WebAccess Application

With just the WebAccess Agent running, you have only one piece of the entire WebAccess system running. You need to get the WebAccess Application up and running as well.

To do so, load the web server and the servlet gateway. The instructions for loading the web server or servlet gateway are different based on the platform you are using. The WebAccess Application needs two components in order to work: a Java servlet gateway and a web server.

Tip

Generally it's a good measure to reboot the server with the web server on it after the installation. Sometimes the WebAccess Application will not seem to behave as it should. Look at the following web server tips for instructions on the steps you might need to take to load the components that support the GroupWise WebAccess Application.


Following are the steps for loading the GroupWise WebAccess Application. Choose the OS you are running the WebAccess Application on, and follow the instructions associated with that OS.

Apache Web ServerNetWare 6.5 Server Platform

To load Apache 2.x on a NetWare 6.5 server, simply type this command:

apache2

The command to unload Apache2 is as follows:

unload apache2

Tomcat Servlet GatewayNetWare 6.5 Server Platform

NetWare 6.5 Apache web servers use the Tomcat servlet engine. The command to load Tomcat 4 is the following:

TOMCAT4.NCF

The Tomcat servlet engine might not be loaded automatically with your Apache web server on the NetWare platform. The Tomcat servlet gateway can be loaded before or after the web server loads. To load the Tomcat servlet gateway, use the following command:

tomcat4

The commands to unload Tomcat are shown here:

java -killall java -exit

Or if you need to be a little more careful because your server is using JAVA for things other than the Tomcat servlet gateway, you need to just kill the Tomcat process. To show and then kill the Tomcat process, use this command:

java -show

The JAVA SHOW command reports the process ID. You can then issue this command:

java killPROCESS_ID

So if the process ID for our Tomcat servlet gateway was 176 as reported by the JAVA SHOW command, our command line would read as follows:

java kill176

LinuxApache Web Server

On Linux there can be different ways to install Apache2, because it can be part of the Linux distribution or can be installed separately for GroupWise only. During the installation of WebAccess, you can choose to install into an existing web server or to create and install a separate instance of Apache.

To start Apache manually on a Linux server with a GroupWise installation of Apache, use the following commands:

/etc/init.d/novell-tomcat4 start /etc/init.d/novell-httpd start

To stop Apache on such a server, use this:

/etc/init.d/novell-httpd stop /etc/init.d/novell-tomcat4 stop

On Novell Open Enterprise Server Linux the installation of Apache is part of the operating system. To start WebAccess manually, you can use the following:

/etc/init.d/novell-tomcat4 start /etc/init.d/apache2 start

To stop Apache on a Novell Open Enterprise Server, you can use this:

/etc/init.d/apache2 stop /etc/init.d/novell-tomcat4 stop

The command paths to load Apache and Tomcat on the Linux server may be different based on the version of Linux you are using, but the syntax should be similar.



NOVELL GroupWise 7 Administrator Solutions Guide
Novell GroupWise 7 Administrator Solutions Guide
ISBN: 0672327880
EAN: 2147483647
Year: 2003
Pages: 320
Authors: Tay Kratzer

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net