Moving WebAccess – Windows

In this chapter, we are moving a WebAccess Agent to a new NetWare server. Since we never run a WebAccess Agent on a server remote from its owning domain, that means we also must move our domain to the new NetWare server. It’s also possible that this domain owns other gateways like a GWIA. If this is the case, and if you plan on moving the GWIA to the new NetWare server as well, we can do this all at one time. However, if you only wanted to move the WebAccess Agent to the new NetWare server, and leave the GWIA on your source server, you would essentially not be moving a domain to the new NetWare server at all. Rather, you would be creating a new domain and WebAccess Agent on the new NetWare server. If this is your situation, stop now and go to the Chapter entitled “Creating a New Domain on Windows to Relocate a Gateway”.

The steps we will take are as follows

  • Unload the existing Message Transfer Agent (MTA) for this domain. We will need exclusive access to the domain database, so we must also unload the WebAccess Agent and any other gateways that belong to this domain.
  • Rename the domain directory to avoid any accidental access while we are relocating the domain.
  • Copy the domain directory structure from it’s current location to the new Windows server using dbcopy or scp.
  • Load ConsoleOne and edit the domain location, agent address and link information if necessary.
  • Configure the MTA on you new Windows server.
  • Load the MTA with a GUI console for the relocated domain for testing
  • Verify that the MTA is communicating with any post offices it owns, and any other domains for which it has direct links.
  • Install the WebAccess Agent software and configure the WebAccess Agent
  • Install the WebAccess Application software and configure the WebAccess Application.
  • Load the WebAccess Agent and Restart Apache and Tomcat


So, let’s see how this all works.


Unload the MTA

First of all, go to the server where your MTA is loaded for the domain that you are moving:

  • NetWare: press F7 at the agent console to unload the agent
  • Windows: if the agent is running as an Application, you can also press F7, or use the File Menu and Exit. If the agent is running as a Service, you must stop the agent from the services applet.
  • Linux: use rcgrpwise command. For example:

rcgrpwise stop DomainName

If you are not certain of the name that is defined for your domain in the rcgrpwise script, first run:

rcgrpwise status

This will show you all agents that the rcgrpwise script controls. Find the name for your MTA and then issue the stop command for your MTA.

Also make sure that no administrators are accessing the domain database through ConsoleOne.

Unload Your WebAccess Agent and Any Other Gateways

Like the MTA, your GWIA and any other gateways that are running under this domain must be unloaded. The instructions are the same as for the MTA. Press F7 where appropriate to unload the gateways, shut down the services on Windows, or stop the daemons on Linux. Make sure all gateways have been shut down before you proceed.

Copy the Files to New Windows Server

Once we are ready to move the domain directory structure to our new Windows server, we will rename the domain directory to avoid any accidental access by administrators using ConsoleOne, NWADMIN, etc. We will copy, not move, all of the files. If needed, you could simply rename your domain directory back to its original name and load your MTA back up on the source server.

Most people will simply connect from a Windows workstation to both the source server and the new Windows server, and then copy the data from the source server to the new Windows location. The domain directory is rarely very large (unless you have a lot of logs saved there), and should copy very quickly.


NOTE: It’s a good idea to look through your domain directory structure for old log files, files in the problem directories, etc. to clean up prior to copying the directory structure. This will ensure that you don’t needless copy unneeded information to the new server.

Edit Important information in ConsoleOne

Now that your domain directory has been moved to the new Windows location, we need to edit the location of the domain directory and fix some information in the agent’s network address configuration.

  1. Open ConsoleOne to edit the properties of the domain you have moved.
  2. Right-click on the GroupWise domain you have moved to your new Windows server, and choose Properties.
  3. Change the location of the domain to the new location’s UNC path – you can browse for this if necessary.
  4. Now, in the dropdown list that shows “Users”, change the setting to “Message Transfer Agents.”
  5. Find the MTA for your domain, right-click and choose Properties.
  6. On the first screen, change the Platform to Windows if necessary.
  7. Now click on the triangle in the GroupWise tab and change to Network Address. Here you must change the IP address to that of the new Windows server.
  8. On the GroupWise tab, change to the log settings. If you have a custom path for the log settings, remove it. otherwise logging will generate an error.
  9. On the GroupWise tab, change to the Message Log Settings tab. As above, delete any custom location you may have defined there.
  10. If you use SSL to communicate between agents, you will need to regenerate your GroupWise SSL Certificate for this server and make the changes on the SSL settings tab.

You can find information on generating your SSL certificates for GroupWise at This information is for GroupWise 8.Similar information can be found for all versions of GroupWise, but the instructions for GroupWise 8 are the same as prior versions.


  1. After you have made all of the above changes, click OK to save the settings.

Installing the GroupWise Agents, and Configuring the MTA on Your New Windows Server

To install the software for your agent, you can use your GroupWise CD, Software Distribution Directory, or simply download new software from the Novell downloads site (

In the root of the location of your GroupWise software, you will see the setup.exe program that will be used for this installation. Our installation here is using GroupWise 8.0. Your agent installation may vary slightly. When you run this program, you see the Window in Figure 5-1.

    1. install1.tiffThe main installation screen

  • Click on Install GroupWise System.
  • Click Yes on the next screen to accept the license agreement.
    1. Click Next on the next screen to do a standard install. You will see the window in Figure 5-2.
    2. Install GroupWise AgentsFigureN2.tiff


  • “Install Individual Components”.
  • Choose GroupWise Agents as an option to install.
  • At the next screen you will be prompted if you wish to install on NetWare or Windows. Of course we will choose Windows here.
  • The next screen will give you the option of where to install your files on your Windows server, and options for the installation.
    • Install and configure SNMP for GroupWise Agents: If SNMP is available and installed on your Windows server, you can configure your agents here for SNMP.
    • Install as Windows services: Most Windows sites will configure GroupWise agents as services. Otherwise the server would need to remain logged in in order for the agents to run.
    1. After you choose the options on this screen you will click next and be presented with the window in Figure 5-3.
      1. configure1.tiffConfiguring the GroupWise Agents

While we are looking at this screen, we should explain its usage so that it’s more easily understood the next time you encounter it. There are a few misconceptions about what is done here, and what you need to put in this location, so we will try to clear those up.

First, this screen is a template for creating new agent startup files (for example the primary.mta file), and your Windows icons or services. When we click the Add button as shown in Figure 5-3 we can enter the information for our domain.

  1. configure2.tifAdding a domain for configuration

By entering this information, we are instructing the installation routine to create us a startup file called cnc.mta with a /home switch of “d:\domains\cnc (on Windows you may need to convert this to a UNC path manual, such as \\server\d$\domains\cnc),

The installation does not validate the “name” you put here and indeed, you can name things here anything you like. For example, rather than naming our startup file “cnc.mta” as shown above, we could just as easily type “domain” in the name field, and the name of the file would instead be domain.mta. If you put in a name that has more than eight characters (for example Caledonia), the file name will be truncated to eight characters. So, if indeed we were to put “Caledonia” in the name of the domain field, we would have a startup file called “caledoni.mta”. If a “caledoni.mta” file already exists, we will now have a “caledoni.mt1” file in that directory.

  1. Next you will be asked for the Windows user for the Service (assuming you are installing the agents as services.
  2. Next you will be presented with a summary screen showing your choices for the install, and the installation will proceed.
  3. When the installation has completed, choose to launch your agent now, and verify that it can see the post offices that it owns.

As long as your MTA was talking IP to it’s post offices (assuming there are any), there should be no problems with communication. If, however, your domain and post office were on the same server, and you had a direct or mapped connection, you will need to edit the links for the post office.

    1. Back in ConsoleOne right-click on the domain and choose GroupWise Utilities|Link Configuration.
    2. From the menu choose View|Post Office Links.
    3. Double-click on the Post Office that cannot be accessed, and fix the link. It should, of course, be a TCP/IP connection, pointing to the IP address and port on the post office’s server. See Figure 5-5
      1. Figurel-d11.tiffChange the Link Configuration

  • If all goes according to plan, your MTA will now show your POA open. Verify all of the links for this MTA (other post offices and domains).


Install the WebAccess software and configure the WebAccess Agent

Now that the MTA for this domain is up and running in testing mode, we will continue to install the WebAccess Agent software and configure the WebAccess Agent on this server.

There are actually three different components that are possible to install for WebAccess. It is by far the easiest on NetWare and Windows if you can do the full install at the same time, with drives mapped to both the location of the WebAccess Agent and the WebAccess Application from the same workstation. If you need to do the installations separately you can. The following installation shows all of the steps in one run of the installation. If you do not do the entire installation at once you will simply see fewer options.

In the internet/webacces directory of your Master SDD you will find the setup.exe installation program for WebAccess. We are assuming in this example that you will be installing both the WebAccess Agent and WebAccess Application on the same NetWare server. If that is not the case, install the portion you need here. The general process is the same. You will just see fewer options if you do not do the entire installation on this server.

  • Run setup.exe in the /INTERNET/WEBACCES directory.
    1. Proceed past the license screen. Here you can choose amongst the WebAccess Agent, WebAccess Application and the WebPublisher Application. See Figure 5-6. We will select them all for our demonstration. Do not check the WebPublisher Application if you do not use GroupWise Document Management and if you do not want to publish your documents through WebPublisher. Click Next.
      1. webacc1.tiffThe WebAccess Installation Screen

  • The next screen allows you to choose the platform and path for your GroupWise WebAccess Agent. On NetWare the default path is z:\system.
  • Next you must confirm the correct IP address or DNS address for your GroupWise WebAccess Agent and the port that you would like to use. The default port number for WebAccess is 7205. You can change this port number if you desire. Of course, you must change the port number if 7205 is being used by another process on that server. Click Next.
  • Next you will see the “WebAccess Agent Gateway Directory” dialog. Be sure to enter the directory name for your current gateway that was moved over. You will be warned that the directory you chose is in use, and be prompted to verify that you wish to use that agent’s settings.
  • The next screen will ask you information for authentication for the agent.

At the next screen enter an eDirectory username and password. This username and password is only used if your GroupWise WebAccess Agent is accessing a post office via a UNC path connection. We suggest that you configure all of your WebAccess Agents to connect to your post offices Client/Server only. Even though your WebAccess Agent should never need this username and password, you must enter one here in order for the WebAccess Agent to function. If your post office connections are all Client/Server only, then the username and password here need not even be a valid eDirectory user. Click Next.

  1. You will next be prompted to enable the Web Console for the WebAccess Agent. You can configure this here, or later in ConsoleOne. If you enable Web Console, you can view the status of your Web Access Agent through a web browser. This screen requires a username and password. Please note that this is neither an eDirectory user nor a GroupWise userid. It is a user that you make up specifically for this purpose, and is not tied to any other userids in eDirectory or GroupWise. If you intend to use GroupWise Monitor, it is convenient to make this username and password the same for all agents that you intend to monitor (WebAccess, MTA, POA, GWIA, etc.). Click Next.
  2. If you are installing WebPublisher, then select the option to “Enable WebPublisher” and define the proxy user and password (this is a GroupWise user – most sites create a specific “WebPublisher” user for this purpose). You will then be prompted to check which libraries should be accessible to the WebPublisher user. If you are not installing WebPublisher, then you can simply click Next without checking the option.
  3. At the installation summary screen, confirm that you’ve configured the WebAccess Agent correctly. Next you will be configuring the WebAccess Application. Click Next.


This is the end of the WebAccess Agent setup, and the next few dialogs will refer to the WebAccess Application to be installed on your Web Server.


  1. Choose the web server you intend to use. Here we can install the WebAccess Application on NetWare or Windows only. If your web server is on Linux, go back here until the first screen where you chose what to install, and uncheck the WebAccess Application. By going back rather than canceling you will avoid having to reenter all of the information we’ve just entered! Here we need to enter the root directory of the web server. Click Next
  2. Choose the default language for your WebAccess Application.
  3. Next you will asked where to locate the WebAccess Application objects for your installation. Since we are moving WebAccess you already probably have these objects somewhere, and it’s useful to keep the same ones. However, remember that these objects simply serve as a nice interface to edit your configuration files. If you do accidentally create a new set in eDirectory somewhere else in the tree, you might get confused later, so try to keep just one set! A good indication that you’ve found the proper spot is a popup that tells you that the objects already exist, and asks you if you wish to use these objects. And yes, of course, you do!
  4. If you have chosen to install the GroupWise WebPublisher, you will go through a similar step as 13 above for your WebPublisher objects. The same information applies for these.
  5. Finally you will be at a summary screen where you can look over your settings one last time before completing the installation.
  6. The installation will start copying files and configuring the WebAccess Application according to the information you provided in the steps above.
  7. If you have special Access Control Rules defined, these are located in the gwac.db file. If you have moved your WebAccess Agent to this server, then these rules will have moved with you. If you are returning to this section from the Chapter on”Creating a New Domain on NetWare to Relocate a Gateway” then you need to copy this gwac.db file from the original gateway directory.


Loading The GroupWise WebAccess Agent


Load the GroupWise WebAccess agent in the Services applet.


Restart IIS to restart the WebAccess Application