Preparing your New Linux Server

Previous Sections

In this wiki we assume that you have already installed and prepared your new Linux server for the move of your GroupWise domain.

While we do not intend to go through all of the steps of installing and configuring your new Linux server, we will point out a few requirements and recommendations for the Linux server.

General Linux Recommendations

For OES, make sure that the following options are installed:

  • NCP™ server
  • eDirectory™
  • Linux user management (if you wish to LUM enable administrators for access to the domain directory structure)
  • GUI libraries (GroupWise dependencies)
  • ncpfs if you are moving your GroupWise domain from NetWare
  • smbfs if you are moving your GroupWise domain from Windows
  • If your server will run a WebAccess Application (the web server component of WebAccess), you must also ensure that Apache2 and Tomcat are installed.
  • GroupWise DBCopy
  • ConsoleOne if GroupWise 2012 or earlier
  • GroupWise Agents


For SLES, make sure the following options are installed:


  • GUI libraries (GroupWise dependencies)
  • Samba Server if you intend to manage your GroupWise 2012 or earlier system later via ConsoleOne on Windows
  • ncpfs if you are moving your GroupWise domain from NetWare
  • smbfs if you are moving your GroupWise domain from Windows
  • If your server will run a WebAccess Application (the web server component of WebAccess), you must also ensure that Apache2 and Tomcat are installed.
  • GroupWise DBCopy
  • ConsoleOne for GroupWise 2012 or earlier
  • GroupWise Agents


We will not cover all of the configuration of an OES11 or SLES11 server in this guide. For either server platform, you should be able to install each of the options list above until you reach GroupWise DBCopy either during your server installation, or after the fact with YaST. The last three items, GroupWise DBCopy, ConsoleOne and the GroupWise Agents must be installed after the server is up and running, and we will cover all of those here.

ConsoleOne and the GroupWise Agents are not required until after we actually move our domain files. It’s practical, however, to just get it all installed now, and be done with it.

Install ConsoleOne

First, if the server in question will have a GroupWise domain on it, we need to install ConsoleOne on Linux. While it’s unlikely that you would ever need ConsoleOne on a Linux server that only houses post offices, it doesn’t hurt to install ConsoleOne on such a server should you so choose. You should download the most current version of ConsoleOne available. Go to See Figure 3-1 for the options for downloading ConsoleOne.


    1. FigureL-D1a.tiffNovell Downloads Page


Click on the file name to go go the download window (in our example this is ConsoleOne 1.3.6h). At the next screen, be sure to choose to download ConsoleOne for Linux.

After the file is downloaded, open a terminal window, change to the folder where the ConsoleOne file is located, and extract the files like so:

tar -xzf c1-136h-linux.tar.gz


NOTE: If you wish to see the files being extracted, you can change the switch above to -xzvf to add the verbose command.


TIP: It is not necessary to type the entire file name when you are extracting files, changing to long directory structure names, launching an installation program, installing an rpm, or the like. Simply type the beginning of a file name and press the Tab key. Linux will auto-complete the name of a file up until the point where it is no longer unique. For example, if I had two files in a directory called c1-136g-linux.tar.gz and c1-136h-linux.tar.gz, typing “tar -xzf c1” and then pressing tab would complete to “cl-136” and stop. I could then type in the “h” and press tab again, and the full name of the file would complete for me.


Once the ConsoleOne files have been extracted, you should have a Linux subdirectory in your extraction location. Change to the Linux directory and execute the following as root:




Most of the questions you are asked should be self-explanatory. When asked which snapins to install, we typically choose “all” just in case we ever need these snapins.


NOTE: You will not see the GroupWise Administration snapins listed here. Those are installed in the GroupWise installation below.


Once ConsoleOne has been properly installed, we will move on to installing some GroupWise files.

Install GroupWise Agents

To install the GroupWise agents, download the Linux software for the version of GroupWise you have. You should be able to find the GroupWise distribution for your version at See Figure 3-2 for downloading software from the Novell download site.


    1. Downloading ConsoleOneFigureL-D1.tiff



Extract the files into a directory of your choosing. This can be the location which you intend to serve as your Software Distribution Directory on this server. To extract the files, open a terminal window, change to the folder where the your GroupWise distribution file is location, and do the following:

tar -xzf gw8.0.1-88138_full_linux_en.tar.gz


In our example, of course, gw8.0.1-88138_full_linux_en.tar.gz is the name of the GroupWise 8.01 distribution file we downloaded. Remember the “tabbing” autocompletion trick we discussed above to avoid having to type in the entire file name.

Once the files have been extracted, you will see a directory structure as shown in Figure 3-3.

    1. GroupWise Distribution Directory StructureFigureL-D2.tiff


run the install script as root. For example:

gwlinux:/grpwise # ./install


NOTE: If you are new to Linux, you will find a difference in how Linux deals with the “search path” of an application. On Windows, if you go to a command prompt and change explicitly to a directory where a program resides on the disk, you simply type the executable name and the program is launched. On Linux, however, if you are in the directory where the application resides, you must proceed the command with ./ – thus above we changed to the directory grpwise, where our install script resides, and in order to execute it, we typed ./install and not simply install.

You will see the screen in Figure 3-4.

    1. The Initial GroupWise Installation Screen on LinuxFigureL-D3.tiff
    1. Choose install products. You will now see the screen in Figure 3-5.
    2. FigureL-D4.tiffChoose your GroupWise Component


  • Choose GroupWise Administration.
  • Choose Install GroupWise Administration
  • The installation will continue, and you will be prompted to click “OK” when the installation has finished.
  • There is no reason to “Configure Administration” so click on the Back button at the bottom of the screen (the right-most button is Exit, the left-most button is Back).
  1. You will now see the screen again from Figure 3-5 above.
  2. Choose GroupWise Agents. We will take this opportunity to point out that in the Linux installation routine there are separate “install” and “configure” steps for each installation option. We will not configure the agents yet. This will be done after we move the files to the server.
  3. Choose Install Agents. The agent files will now install. Exit the installation program once the agents have been installed.

At this point, we have installed the necessary software to administer GroupWise and to load our MTA upon completion of the move. No configuration files or startup scripts have been created at this point.

Install DBcopy

That was simple. However, the most important part of our installation for the migration has not yet been installed. That component is the GroupWise DBcopy application. DBcopy is a utility that was originally developed by Novell as a backup tool. DBcopy can copy GroupWise databases while they are open, thus ensuring a good backup without worrying about files being skipped because they are open. Over the years, DBcopy has been optimized to also include functionality needed for a move or migration of GroupWise from one location to another.

In order to install DBCopy, we will need to drop to a terminal window.

  1. In the terminal window, change to the directory where your extracted GroupWise distribution files are located. As you will notice in Figure 3-3 above, there is an admin directory in this directory structure.
  2. Change to the admin directory, and you will notice a number of files, including one for novell-groupwise-dbcopy. The remainder of this file name will vary, depending on the version of GroupWise that you are installing.
  3. We will now install DBCopy by executing the following command:

rpm -Uvh novell-groupwise-dbcopy-8.0.1-88138.i586.rpm

Of course the above file name is the one for our distribution. Your file name may vary.

  1. Once the rpm has been installed you will be returned to the terminal prompt.
  2. You can verify that DBCopy has been installed by typing:

ls /opt/novell/groupwise/agents/bin


Along with the GroupWise agents that we installed earlier, you will also see the DBCopy program in the directory.

With these three programs installed, we can now start our GroupWise components move. We will begin with a domain move in the next chapter.

Throughout this Section on moving to a new Linux server, we will be discussing three different types of servers: NetWare, Linux and Windows. Unless the information is specific to a particular server OS, we will simply reference the “Source” server. So, no matter where you are “coming from” you will be able to get your domain moved to a new Linux server.

First, let’s look at some of the reasons why you might be moving your domain to a new Linux server, and point out which chapters of this section will be for you!

  • Your domain is already on Linux, but you are upgrading to new hardware, reconfiguring your network, or any other myriad of reasons why you might need to relocate GroupWise.
  • Everything is moving to a new Linux server. If you are moving all of your GroupWise system to a new Linux server, and you have a small system, you may be moving your domain, gateways and post office together to Linux in a very short period of time. If you are moving a domain that has no gateways (for example, a primary routing domain, or a domain that only owns post offices), we will discuss how to do this in “Moving a Domain with No Gateways – Linux”.
  • You wish to move your GWIA to Linux. As you probably know, Novell’s Best Practices for GroupWise highly discourages the idea of having a gateway on a server remote from its domain. Any time we put a gateway on a server, we need to have a domain there. So, if you wish to move your GWIA to Linux, you will need to move the domain that owns that GWIA as well. For some sites, moving the domain and GWIA together is quite simple, and we will go through the steps for this in the chapter “Moving a GWIA – Linux”. For others, you might need to create a new domain and effectively install a new GWIA, rather than actually “moving” the domain and existing GWIA. We will discuss how to do this in the “Creating a New Domain on Linux to Relocate a Gateway” chapter.


As we move through this section on Linux, we will address each of these ways to move a domain to a new Linux server.

Next Sections