Gordon Welling
Admin Group
Manager Technnical Support Services
Joined: 11-December-2003
Location: Canada
Posts: 502
|
| Posted: 25-January-2007 at 4:12pm
|
|
|
Question: I am retiring my existing NetWare 6.0 / GroupWise 6.5 server and migrating my GroupWise system to a new NetWare/OES 6.5 server running GroupWise 7.0.1. How can I move my Omni Mobile server to my new NetWare/GroupWise server?
Answer: To migrate or move the Omni Mobile server to a replacement server platform, the administrator must:
- Login into WebAccess as the Omni Mobile admin before GroupWise is migrated and review the license information. Determine if any of the "Server" information will be changing. If so, contact Omni support to obtain a replacement license.key file.
- Stop Tomcat (or the W3SVC on Windows servers running GroupWise 6.5.x) on the retiring server.
- Make a copy of the following files:
- omnimobile_admin.script found in the data folder
- omnimobile.properties found in the classes folder
- license.key found in the classes folder
- Migrate the GroupWise system to the replacement server and confirm that you can login in as the Omni Mobile admin account in WebAccess.
- Stop Tomcat (W3SVC on Windows servers) on the replacement server.
- Copy the omnimobile_admin.script from the original server to the data folder on the replacement server, normally found in:
- sys:tomcat\#\data (NetWare)
- /var/opt/novell/tomcat4/data (SUSE)
- c:\novell\java\data (Windows / GW 6.5)
- c:\novell\tomcat5.5\data (Windows / GW 7)
- Edit the omnimobile.properties file from the original server, and copy the "authorized.users= " line into the omnimobile.properties file on the replacement server, normally found in:
- sys:tomcat\#\webapps\gw\WEB-INF\classes (NW / GW 7)
- sys:tomcat\#\webapps\ROOT\WEB-INF\classes (NW / GW 6.5)
- /var/opt/novell/tomcat4/webapps/gw/WEB-INF/classes (SUSE)
- c:\novell\java\servlets (Win / GW 6.5)
- c:\novell\tomcat5.5\webapps\gw\WEB-INF\classes (Win / GW 7
- Copy the original license.key file (if the Server information did not change) or the replacement license.key file into the classes folder on the replacement server, normally found in:
- sys:tomcat\#\webapps\gw\WEB-INF\classes (NW / GW 7)
- sys:tomcat\#\webapps\ROOT\WEB-INF\classes (NW / GW 6.5)
- /var/opt/novell/tomcat4/webapps/gw/WEB-INF/classes (SUSE)
- c:\novell\java\servlets (Win / GW 6.5)
- c:\novell\tomcat5.5\webapps\gw\WEB-INF\classes (Win / GW 7 - Start Tomcat (W3SVC on Windows servers) on the replacement server, login into WebAccess as the Omni Mobile admin and confirm that everything looks normal.
- Click the "Update" button once to force a policy update for the Omni Mobile server.
NOTE: Refer to "How to Upgrade Omni Mobile or GroupWise WebAccess with Omni Mobile Installed" in the "Omni Mobile Admin Guide" for the commands that can be used to correctly stop and start Tomcat (or W3SVC) on the various server platforms.
Each Omni Mobile user will also have to make a few changes:
- Login into WebAccess on the replacement server, go to Omni Mobile (tab or icon), review all of the user profile settings and click "Update" at least once. (NOTE nothing has to be changed, the user needs to force an account policy update to ensure that data will flow to the device again).
- Run the Omni Mobile client on thier device(s) in "Work Offline" mode.
- Go to Client Options and change the Server URL so that it is correct, e.g. if the original GroupWise system was 6.5 and the replacement GroupWise system is 7.0.x, then the Server URL needs to be changed from http:// or https://<email server DNS name or IP address>/servlet/webacc to http:// or https://<email server DNS name or IP address>/gw/webacc.
- Save the client options and then switch to "Work Online" mode. That should force the Omni Mobile client to connect to the Omni Mobile server and check for new policies and data.
Edited by Gordon Welling on 25-January-2007 at 4:15pm
|
Omni Web Forum : GroupWise for PDAs and Smart Phones ~ Omni Mobile : Omni Mobile Server for GroupWise Synchronization
Topic: How to move the Omni Mobile server
