Here are the steps I followed for a successful GroupWise migration from NetWare to OES2.
Setting Up OES2 and ConsoleOne
1. Perform an eDirectory Health Check and make sure it is successful.
2. Run the Deployment Manager to properly extend the schema for OES2 and eDirectory 8.8.
3. Install and configure OES2 (basically SLES10.1 with the OES2 Products CD).
During the install, I chose Add on Products, inserted my OES2 CD, and allowed the setup to create the inventory of the OES2 CD. I then chose ALL OES2 Services for this particular install. This may vary for you. Remember – DNS and DHCP are now eDirectory-integrated on your OES2/SUSE LINUX Enterprise Server (yes!)
4. Create your NSS Volume (vol1) with NSSMU from the command line. Remember, per Best Practices this should be a separate disk created with EVMS.
Note: This does NOT have to be NSS. I prefer NSS for multiple reasons: I am an eDirectory, NCP, Novell Client junkie and always will be …
5. Install ConsoleOne 1.3.6h on the new OES2 Server.
Before copying databases to OES2:
1. Bring down the GroupWise System on the existing Netware 6 Server.
2. Delete the POA, MTA, GWIA and WebAccess objects.
3. At this point I ran my database maintenance and rebuild both Domain and PO.
1. Copy the domain database to the SLES Server, using WinSCP to your new NSS volume. (I’m sure there are many other ways/utilities to do this, but I prefer WinSCP.)
2. Copy the Post Office database to the SLES Server utilizing WinSCP to your new NSS volume.
Note: This is a great time to clean up your directory structure from years past. For example: Clawson_IndyDomain to just domain / Indpls_Po to just PO …
Important: The next step is a Linux case-sensitive issue: Remember that Linux is case sensitive, so the databases need to be all lowercase:
3. Run chcase, on both the PO and the Domain, in order to change both databases to lowercase. For example:
./chcase ?rd /path to postoffice
For more information, see http://www.novell.com/coolsolutions/tip/9980.html
4. Triple-check to make sure this process worked!
Running the GroupWise Setup
1. Run the GroupWise setup from the CD or download and run it from www.novell.com. In my case, I was upgrading GroupWise 6 to 7. (I could have upgraded the system before moving it – this is your decision.)
2. Choose update an existing system and point it to the new location on the OES2 Server for the domain database. For example, /media/nss/VOL1/grpwise/domain
3. Run through the install of the following components: POA, MTA, and GWIA.
4. Once this completes, do NOT start the services.
5. Open ConsoleOne from the OES2 Server Console and go through each agent, domain, and post office. This is critical. You’ll want to check to make sure your paths to the databases are correct and that the link configuration is OK. I also check the IP address of the agents, as they sometimes still want to point back to the old server.
6. Run a rebuild on the Domain and Post Office Databases – this should write the new settings correctly.
Setting Up WebAccess
Now on to the WebAccess Agent. This step is critical – you need to know the following things:
- How to install WebAccess Application on OES2
- How to install WebAccess Application on SLES10SP1+OES2 Addon
- How to install WebAccess Application on Open Enterprise Server 2 (Linux-based)
In OES2, there will not be any option to use GroupWise instance of Apache and Tomcat. Follow the steps below to make the GroupWise WebAccess application work with Novell Tomcat5 (although Tomcat5 may also be installed on the server).
1. Launch Shell Konsole.
2. Browse to the GroupWise Software Directory using the cd command.
3. Enter this command:
4. Click Install Products.
5. Click GroupWise WebAccess.
6. Click Install WebAccess Application.
7. Once this completes, click OK.
8. Click Configure WebAccess Application.
9. Follow the prompts and change the Apache path to “/etc/apache2/conf.d”
10. Change the Tomcat path to “/var/opt/novell/tomcat5/webapps” (Make sure that it reads tomcat5 and not tomcat4.)
11. Follow the prompts to complete the install.
12. Once this completes, edit the /etc/apache2/conf.d/gw.conf file and comment out the following line by putting a # symbol at the beginning of the line:
JkMount /gw/* ajp13
13. Below the above line, type this:
ProxyPass /gw/ ajp://localhost:9009/gw/
Make sure that it is 9009 and not 8009. 8009 is used in SLES10 without the OES2 add-on. In OES2, the 8009 port is used by Novell Remote Manager.
14. Save the file.
15. Run this command: rcapache2 restart
16. Run this command: rcnovell-tomcat5 restart
17. Launch the browser and run “http://IPAddress/gw/webacc” to test WebAccess Application.
Once this is complete, you should be able to start all agents from the console by running “/etc/init.d/grpwise start”. You will see all five agents start up successfully!
You can use a ZENworks application and change the IP address that the GroupWise Client is trying to connect to. I use a registry hack and update the registry entry. You could also use DNS to do this.
Firewall or Spam Filter
You may also need to redirect port 25 traffic to your new GroupWise Server on the inside.