“I've heard it called by different names. All over the world, but it's all the same.” We interrupt your summer cruisin' with this flash. GroupWise 2014 is simple to upgrade and the 'dot oh' release is proving very stable indeed!!
This article will present the process for upgrading a GroupWise 2012 post office which is running alone on a server. Alone, in this case means there are no domains/gateways running on the server. Also assumed here is the parent domain for the post office to be upgraded exists on a different server from the GroupWise 2012 post office and that it has already been upgraded to GroupWise 2014. Finally, this article assumes the upgrade is an in-place upgrade on a SLES11 server with no OES.
Why no OES? Because what's the point?! OES for GroupWise was great when you needed ConsoleOne to connect to NSS volumes, but now with GroupWise 2014 there is no need for ConsoleOne. And who needs the overhead, besides EXT3 performs very well on SLES11. Does that mean you must move your GroupWise system from OES11? NO. But when the time comes consider SLES over OES for GroupWise.
The first task is to download and expand the GroupWise 2014 code.
tar -xzf gw14w14.0.0_full_linux_multi.tar.gz
Once the code is downloaded and expanded, change to the code directory:
At this point, run:
Select English, Enter
Select Installation, Enter
Select Agree, by typing 'A'
Select GroupWise Server, Enter
Select Install, Enter
At this point, the installation will shut down the GroupWise 2012 post office and Document Viewer Agent. It will then install the gwadminservice and rpm's for GroupWise 2014. Precisely it will:
Then a “Press any key to return . . .” will be left behind.
Press Any Key
Now you can run an rcgrpwise status which will show all agents running
rpm -qa | grep novell
ps -eaf | grep gw
Note: The gwdva appears to bind to the IP of the server and not the secondary IP of the post office.
Changing gwdva to run on Post Offices IP Address
How to make the GWDVA to listen on the same IP Address as its post office. This may be a secondary IP Address. This is done by going to the gwdva configuration file located at:
gwadminutil services -l
This will provide you a list of services running for GroupWise 2014 as well as the path to the executable and the startup.
Its at this point, we get to use a bit of the new GroupWise 2014 console to finish the upgrade. Technically, the upgrade is finished in the sense the database will register as 1400. But we still need to activate the admin port on the server with the post office we just upgraded. And without an admin port, you lose some of the features of GroupWise 2014.
You will not be able to:
So let's finish up.
Now let's verify we actually had success.
Go to the GroupWise Administration Console, Overview.
You will now see the post office no longer has the (2012) next to it.
Its been upgraded at this point both database and service.
Next, while in the GAC, you will want to add the DVA.
System, Document Viewer Agent, New
Fill in the information:
Next go to:
Post Office Agents, Select a POA, go to Document Viewer Agent tab
Done, or repeat for next post office.
Now you can run the Configure, if you want.
Now the last step. Stop/Start the agents and reboot the server and verify all comes up as expected. Then verify end user login with client, webaccess and mobile devices.
Rinse and Repeat for the next post office that has a GroupWise 2014 parent domain.
As you can see, upgrading a GroupWise post office to 2014 is very easy on Linux. And because its so easy it will get you back to your summer fun so you can sing along with: “There's only one way to rock.”
Got comments or article ideas? Need help GroupWise? Drop me a line at: Gregg@HinchmanConsulting.com. “The Force is strong in this one.”