Novell Cool Solutions

Consultant’s Corner: Upgrade GroupWise 2012 Post Office to GroupWise 2014

Gregg Hinchman

By:

June 5, 2014 11:59 am

Reads:2,572

Comments:3

Score:5

Print/PDF

“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!!

TIP: Did you know that you can upgrade just the Primary domain of your GroupWise System to 2014 and be able to use the GroupWise Administration Console (GAC) to administer your entire GroupWise system? Of course there are a few exceptions such as manual rebuilds of non-GroupWise 2014 domains and post offices. Just do the rebuild to a temporary location on the primary domain GroupWise 2014 server then scp (copy) the db over to the GroupWise 2012 (or v8) domain/post office. Stop the agents, insert the db (wpdomain.db/wphost.db), start the agents. So you cannot use the GAC to do the rebuild. But you can do just about any other day-to-day administration.

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.

  1. Current code for GroupWise 2014 is: gw14.0.0_full_linux_multi.tar.gz
  2. Save in a temporary location such as: servername:/tmp
  3. To expand, open a terminal and type:

tar -xzf gw14w14.0.0_full_linux_multi.tar.gz

Figure 1:

Figure 1:

Once the code is downloaded and expanded, change to the code directory:

cd /tmp/w14.0.0-115243_full_linux_multi

At this point, run:

./install.sh

Figure 2:

Figure 2:

Figure 3:

Figure 3:

Select English, Enter

Figure 4: Select English, Enter

Figure 4: Select English, Enter

Select Installation, Enter

Figure 5: Select Installation, Enter

Figure 5: Select Installation, Enter

Select Agree, by typing ‘A’

Figure 6: Type 'A' to Agree

Figure 6: Type ‘A’ to Agree

Select GroupWise Server, Enter

Figure 7: Select GroupWise Server, Enter

Figure 7: Select GroupWise Server, Enter

Select Install, Enter

Figure 8: Select Install, Enter

Figure 8: 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:

  1. Shut down agents running
  2. Load/Read repository data
    1. This will look to the SLES11 repository locations. If it cannot reach them it will error out. This may mean either disable repositories or set Proxy Server.
  3. Install new novell-groupwise-server
  4. Remove old: novell-groupwise-agents and novell-groupwise-dva
  5. It will upgrade: novell-groupwise-gwha and openmotif22-libs
    1. These two items will undergo an architecture change to x86_64
  6. Once these are stated, it will run through the installation.
  7. At the end of the installation, it will load up the new:
    1. gwadminservice
    2. gwdva
    3. po.dom
Figure 9: Installation process for GroupWise Server, part 1

Figure 9: Installation process for GroupWise Server, part 1

Figure 10: Installation process for GroupWise Server, part 2

Figure 10: Installation process for GroupWise Server, part 2

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
Type:

rpm -qa | grep novell

You will find the 2 new packages running

Type:

ps -eaf | grep gw

You will see the configuration and service information for both the:

  1. gwadminservice
  2. gwdva
    1. and its 5 workers

      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:

  1. /opt/novell/groupwise/agents/share
  2. Open the gwdva.dva
    1. Find the remarked line: /ip-[address]
    2. Below it, unremarked, Type in:

      – – ip-IPofDVA

      This line is ‘dash dash ip dash Secondary IP Address for Post Office
  3. Save, Exit
  4. In a Terminal Type:
    1. rcgrpwise stop
    2. Then when the agents have stopped, type:
    3. rcgrpwise start
    4. Finally, to verify the change was taken, type:
    5. ps -eaf | grep gw
Changing gwdva to run on Post Offices IP Address

Changing gwdva to run on Post Offices IP Address

Type:

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.

Figure 11: Various commands to show GroupWise 2014 Services are running

Figure 11: Various commands to show GroupWise 2014 Services are running

Note: At this point, the startup files are in the /opt/novell/groupwise/agents/share directory. But this is not the default location for these files in GroupWise 2014. In GroupWise 2014, they are stored in the directory where the wphost.db for the post office is stored. The post office directory.

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:

  1. Stop/Start the POA Agent from the GAC
  2. No maintenance of the Post Office from the GAC

So let’s finish up.

  1. In a browser:
  2. Go to the IP Address of the POA, port 9710, gwadmin-console/install
    1. https://192.168.91.142:9710/gwadmin-console/install
  3. At the authorize screen, go to the server of the Post Office,
  4. Open a Terminal and Type the gwadmin-ipc authorize with the code given
    1. gwadmin-ipc authorize uqscqn4nXbY
    2. This will return you the code in the terminal
  5. Next go back to the browser where you will see the gwadmin-console/install screen
  6. Select the “Upgrade an Existing Domain or Post Office to GroupWise 2014
  7. In the Upgrade screen you will see the Post Office listed. Specifically, you will see the Admin Port.
  8. Select Next
  9. In Credentials, Add the Primary Domain MTA IP Address, Admin Port, Admin Name and Password
  10. Select Next
  11. In Summary, Note the information about the Post Office
  12. Select Finish.
  13. Success!!
Figure 12: IP Address of the Upgraded POA, port 9710, gwadmin-console/install

Figure 12: IP Address of the Upgraded POA, port 9710, gwadmin-console/install

Figure 13: gwadmin-ipc authorize on Post Office Server

Figure 13: gwadmin-ipc authorize on Post Office Server

Figure 14: gwadmin-console/install, Select Upgrade an Existing Domain or Post Office

Figure 14: gwadmin-console/install, Select Upgrade an Existing Domain or Post Office

Figure 15: Upgrade of Post Office, Note the Admin Port for the POA, Select Next

Figure 15: Upgrade of Post Office, Note the Admin Port for the POA, Select Next

Figure 16: Credentials, Add the Primary Domain MTA IP Address, Admin Port, Admin Name and Password

Figure 16: Credentials, Add the Primary Domain MTA IP Address, Admin Port, Admin Name and Password

Figure 17: Summary, Note the information about the Post Office, Select Finish

Figure 17: Summary, Note the information about the Post Office, Select Finish

Figure 18: Success! At this point, you have successfully upgraded the post office

Figure 18: Success! At this point, you have successfully upgraded the post office

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.

Figure 19: System Overview showing PO2 upgraded to GroupWise 2014

Figure 19: System Overview showing PO2 upgraded to GroupWise 2014

Figure 20: Properties of PO2, Database Version 1400

Figure 20: Properties of PO2, Database Version 1400

Next, while in the GAC, you will want to add the DVA.
Go to:
System, Document Viewer Agent, New

Figure 21: Add new Document Viewer Agent

Figure 21: Add new Document Viewer Agent

Figure 22: Add new GWDVA information

Figure 22: Add new GWDVA information

Fill in the information:

  1. [PO Name] DVA
  2. Description
  3. IP Address
    1. which may be the servers or the secondary if you changed the DVA configuration file.
  4. Port
    1. which should be the default or the SSL default

Next go to:
Post Office Agents, Select a POA, go to Document Viewer Agent tab

Figure 23: Properties of POA, Document Viewer Agent tab

Figure 23: Properties of POA, Document Viewer Agent tab

  1. Select the Add Document Viewer Agent
  2. Select the Document Viewer Agent
    1. The one for that post office per your previous setup in System, Document Viewer Agents.
  3. Save
Figure 24: Set the new DVA

Figure 24: Set the new DVA

Done, or repeat for next post office.

Now you can run the Configure, if you want.

  1. Select Configure, Enter
  2. You will have a URL listed. The first one is the /install/login.
  3. Nothing will really get configured per se.
  4. If you want to configure the gwha to call your *.POA configuration files from the post office directory, you will have to manually set that up.
  5. You can back out/exit from the ./install.sh at this point.
Figure 25: Select Configure

Figure 25: Select Configure

Figure 26: URL's for Install and Administration

Figure 26: URL’s for Install and Administration

  1. First drop a copy of your configuration file in the post office directory.
  2. Second go to:
    1. /etc/opt/novell/groupwise/gwha.conf
      1. and change the “STARTUP” path to the post office directory.
  3. Stop/Start the post office.
  4. Type:
    1. gwadminutil services -l
    2. and verify the path.
  5. That’s it.
upgradegwpo_img27_2

Figure 27: Shows the Startup Path to the POA file changed

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.”

1 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 5 (1 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Tags: , , ,
Categories: GroupWise, Technical

3

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

3 Comments

  1. By:millenj

    From reading this, you can upgrade a GroupWise 8 PO or Domain server to 2014 without interrupting the other POs?

  2. By:hschoene

    Yes, you can use SLES-only for GW2014, not OES, but also with earlier versions of GW and ConsoleOne on Linux (or redirected X to a windows-machine with Xming). But what about clustering GW-Ressources?

  3. By:petergwapo

    Cant find GWDVA.DVA, why? Need help .

Comment

RSS