Creating a New Domain on Linux to Relocate a Gateway

Wikis > Caledonia Private Wiki > Moving GroupWise > Moving GroupWise to or on Linux > Creating a New Domain on Linux to Relocate a Gateway

Previous Sections

In earlier chapters we moved a domain and gateway to a new Linux server. There will be times when you wish to relocate a GWIA or a WebAccess Agent to a new Linux server, but the owning domain cannot be moved. In this case, rather than actually moving your gateways, you will create a new domain on your new Linux server and install a new GWIA or WebAccess Agent on that server.

Here we will create the domain on our new Linux server. Afterwards, we will go back to either Chapter 5, to the section entitled “Install the GWIA software and configure the GWIA” or to Chapter 6, to the section entitled “Domain Directory Structure” to complete the installation of the agent of your choice.

As we discussed at the beginning of this section, you should never separate a GWIA or a WebAccess Agent from its owning domain. You might be in one of those situations where you want to get your feet wet with Linux by putting only your GWIA or your WebAccess Application and Agent on a Linux server. This is indeed an excellent way to get some Linux experience. Here are a couple of other reasons why you might create a new domain on Linux, rather than migrating an existing one:

  • You wish to put a GWIA or WebAccess Agent on your new Linux server, but your current gateways are owned by the only domain in your system. This is a perfect time to do two things: separate your GWIA or WebAccess Agent from your primary domain; and have a second domain as an online “backup” of your system (you can recreate your primary domain from a secondary domain in case of catastrophic failure and we always recommend at least two domains in a GroupWise system).
  • You already have your gateways in a separate domain from your post offices, but you only want to move one gateway (GWIA or WebAccess Agent), and they both belong to the same domain.

In either of those cases creating a new domain on the new Linux server makes perfect sense. We will need to attach to the primary domain in order to create a new domain.

There are many ways to do this. Let’s look at our possibilities (and if you need help with how to attach to your servers, see “Creating Mount Points on Linux to Other Servers”):

  • Primary Domain on NetWare: If your primary domain is on NetWare, chances are you are using ConsoleOne on Windows to manage it.
    • If your new Linux server is OES2, and you are presenting your GroupWise files via NCP, you can simply map a drive to that server in the same fashion that you map drives from Windows to your NetWare server.
    • If your new Linux server is SLES10, and you have enabled a Samba share for the location of the new GroupWise domain, you can map a drive to the new Linux server from Windows as a Windows drive.
    • You can also use ncpfs to mount a drive directly from the Linux server to the NetWare server, and create the new domain via ConsoleOne on Linux.
  • Primary Domain on Windows: With the Primary Domain on Windows, you can do the following:
    • If you are using a Samba share on your new Linux server, map a drive directly from the Windows server to the Linux server and create the domain from ConsoleOne on the Windows server.
    • If you have NCP available on your OES2 server, map a drive from the Windows server that runs Novell Client 32, and create the new domain on Linux from ConsoleOne on the Windows server.
    • Use smbfs to connect from the Linux server to the Windows server and use ConsoleOne on the Linux server to create the domain.

Primary Domain on Linux: If your Primary domain is on Linux, connect to your new Linux server from the Primary Domain server. Instructions on connecting to your new Linux server can be found in “Tips and Tricks for GroupWise on Linux”, in the Section on “Creating Mount Points on Linux to Other Servers”.


If you are creating a new domain for either a GWIA or a WebAccess Agent, follow these instructions, and then move on to the section for “Install the GWIA software and configure the GWIA” or “Domain Directory Structure” in the previous chapters.

Back when we discussed “Dealing with Case Sensitivity” we discussed the need for your domain directories on NetWare and Windows to also be all lowercase for a mixed OS system. If you have not yet changed the case for your primary domain directory, please download the Change Case utility as described in that section and change the case for your primary domain directory structure.

The steps we will take to create our new domain are as follows:

  • Load ConsoleOne and connect to the primary domain.
  • Create a new Secondary Domain on Linux
  • Configure the MTA on Linux.
  • Load the MTA with a GUI console for the new domain for testing
  • Verify that the MTAs for the primary domain and the new secondary domain are communicating with each other.


After we have finished with these tasks, we can return to the chapters for the gateways above at either “Install the GWIA software and configure the GWIA” or “Domain Directory Structure”.


So, let’s see how this all works.


Create Your New Domain in ConsoleOne

It’s time to create your new domain. First we need to open ConsoleOne. Depending on your setup, and what you decided above on how to connect to both the primary domain server and the new linux domain location, open ConsoleOne either on Windows or Linux and connect to your Primary Domain.

    1. Right-click on the GroupWise System globe and choose New>Domain. Figure 7-1 will appear. Fill in the information for your new domain. Our examples show ConsoleOne on Linux.
      1. Figurel-d18.tiffCreate GroupWise Domain


  • Note that in our figure we have chosen to configure our link. So we will be presented with some additional windows that assist us in this. On the MTA Link screen, choose TCP/IP and click Next.
    1. Now put in the IP address and port information for your MTA. We recommend that you keep the default ports for the MTA and HTTP monitor unless you are using these ports for something else (Figure 7-2).
      1. MTA NetWork Address screenFigurel-d19.tiff



  1. Now that your domain has been created, in the dropdown list in ConsoleOne that typically shows “Users”, change the setting to Message Transfer Agents.
  2. Find the MTA for your new secondary domain, right-click and choose Properties.
  3. Now click on the triangle in the GroupWise tab and change to Network Address. Make special note of the HTTP port that is defined for this agent. By default, the HTTP port for the MTA is 7180. As we noted earlier in this book, since we will not have a GUI console for the MTA, you will want to ensure that you have the HTTP monitor configured properly so that you can access it for monitoring your MTA. If there is nothing in the HTTP port field, put 7180 (or another port of your choosing).
  4. Now, on the GroupWise tab, change to the Agent Settings screen. Notice the HTTP Monitor settings. If you have never enabled the HTTP monitors for your agents, you will need to decide on a good userid and password for the HTTP monitors. Please note that this is neither an eDirectory user nor a GroupWise user. This is an entirely made up user and password solely for the use of the HTTP monitors. If all administrators in your organization will have rights to use the HTTP monitors, then it is a good idea to have the same userid and password for all agents. If you need to limit rights to some agents to various groups, set up a userid and password for each group of agents that will be monitored. Enter the userid and password that you have decided on here in this screen.
  5. After you have made all of the above changes, click OK to save the settings.

Configuring the MTA on Your New Linux Server

Now we will go back and configure the agent for your new Linux server. The configuration process will create a new startup file for the MTA, and configure the agent to launch upon startup.

In a terminal window, go back to the location where you extracted your GroupWise distribution above in “Preparing your New Linux Server”. Run the install script as root. For example:

gwlinux:/grpwise # ./install


  • Choose Install Products.
  • Choose GroupWise Agents.
  • Choose Configure Agents.
  • At the License Agreement screen, accept the license.
  1. The next screen will look very familiar to GroupWise administrators (see Figure 7-3). This is where we list the agents that will run on this server to create startup files and the startup script for Linux.


    1. Figurel-d7.tiffGroupWise Agents Configuration


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 gatedom.mta file), and for configuring your gwha.conf file. Let’s take the example of our groupwise system. Our domain is called CNC. If we want to create a new startup file for the CNC file, and place it in our gwha.conf (provided that we checked the option above to “Launch the GroupWise agents on system startup”), we would click the Add button as shown in Figure 7-4 and enter the information for our domain.

  1. Enter the information for your domain, using the local Linux path (see Figure 4-4)


    1. Domain PathFigurel-d20.tiff



By entering this information, we are instructing the installation routine to create us a startup file called cnc2.mta with a –home switch of “/grpwisedomains/cnc2, place it in the /opt/novell/groupwise/agents/share directory and include the information in the gwha.conf file.

  1. After your domain information is entered, click next to move on to the startup screen.
  2. You will be asked if you wish for your agent to load on startup. This box is already checked, but really just looks like a red box. You will notice that if you click on the box, it becomes white (unchecked) and clicking again will recheck the box. It is advisable to have your agents load on startup.
  3. Click Exit to leave this setup, and then click the Exit icon (at the bottom right of the screen) to leave the GroupWise installation program.


When you perform these tasks, a startup file is created for the domain’s MTA, and if you chose to launch on startup, symbolic links were created in the proper run level directories to start the agent automatically. Looking at the /opt/novell/groupwise/agents directory you will see directories named bin, lib and share. Under bin you will see the agent executables, as well as default startup templates. Under the share directory are a couple of directories, and the cnc2.mta startup file that was created by our installation. Let’s run this agent now and see what it looks like.

Starting the GroupWise MTA with the GUI for Testing

The first time we start a new agent on a Linux server, we like to start it with a GUI console to test that everything is working properly. It’s important to know that you will not run your agents with the GUI console as standard practice. We will load our MTA up for the first time with the GUI console solely to verify that there are no problems with our installation.

The easiest way to start the GUI agent is as follows:

From a terminal window, change to the /opt/novell/groupwise/agents/bin directory. From here, type the following:

./gwmta –show @gatedom.mta &

This should bring up the agent screen as shown in Figure 7-5.

    1. The new MTA for the “Gateway” domainFigurel-d21.tiff



Verify that the Gateway domain shows the Primary Domain open, and that the Primary Domain MTA sees the Gateway doman as open as well.

We will leave our MTA loaded with the GUI console for now while we create and configure our GWIA or WebAccess Agent.

If you wish to create a GWIA on this server, go back to Chapter 5, to the section entitled “Install the GWIA software and configure the GWIA”. If you intend to create a WebAccess Agent on this server, go to Chapter 6, to the section entitled “Domain Directory Structure” to complete the installation of the agent of your choice.

Now that we’ve covered just about every way imaginable to get a domain to a new Linux server, we’ll move on to the really hard part – moving your post office to a Linux server.