This document describes best procedures for upgrading Presence from an earlier version.
As with all Java software The JRE used can change between versions. For this reason some extra care should be taken to ensure compatibility with current JDBC drivers, etc.
The following should be done before attempting to run the installer.
Suspend Presence Tasks
Ensure that all Presence tasks on the live task queue are suspended. We do not want them to automatically resume when the server restarts.
Launch Task Manager and check that channelman.exe is not running - if it is, right click on the process and choose "End process tree".
Stop the Presence Server, Database Server and HTTP Server (if running) via the Heartbeat Client. When these services have stopped, use the Windows Services controller to stop the Presence RPC Server service and the Presence Viii Heartbeat Server service:
Prior to any upgrade, a backup of the database should be taken. To do this, copy any files in the directory "res\database" ending in .wal or .dbn for Presence V3.x and files ending with .lck - .lobs - .log - .properties and .script for Presence V4 to a separate drive. Note that this can only be done if the database service is stopped (see above).
At this point we also recommend performing a database compact using the utility named "databasecompactor.exe" located in the "bin" directory of the Presence installation (Presence Version 3.x only)
At this stage it is okay to run the installer (presence_viii_installer.exe). For instructions, refer to the Installation Guide.
note: If The progress bar gets stuck this could be due to a problem in the Installanywhere.
If this occurs then it is advisable to go to:- Start - Control Panel - Add or Remove Programs and uninstall Presence Viii
This clears something in the registry theat then allows the install to take place. Though the uninstall does not remove the res folder it is advisable to back it up first.
When the installer is complete, you should be prompted to start the Presence components. Ignore this and exit the installer. Use the Windows Services manager to restart the Presence RPC Server and the Presence Viii Heartbeat Server services. This will cause the Database server, Presence server and HTTP Server (if used) to resume.
Once the various services have had time to start, you should be in a position where Presence is running but no Tasks run from the Live Task Queue:
Start Admin Client
At this point it is safe to start the Presence Admin Client via Start > Programs > Presence Viii > Administration > Presence Admin Console.
Test JDBC Drivers
Work through your Database Resources (see image below). Open each one and click the "Test" button.
If the test fails, this is likely to be due to a conflict of versions between the JRE and the JDBC driver. Consult the provider of the JDBC driver to obtain one that is compatible with the JRE shipped with the version of Presence you are using.
Resume Queued Processes
Once all of your database connections are verified, go ahead and resume the Queued Tasks that were suspended earlier. You can do this one by one or all at once by selecting multiple Tasks, depending on which makes you more comfortable.
If Tasks have one or more Schedule Nodes attached to them and "Catch up" is enabled they will run now if they were due to run while the Server was disabled. Otherwise they will be queued to run at the next run time. If no Schedule Node is attached the Task will run within 30-60 seconds.
Congratulations - the upgrade process is now complete.
Your upgrade should go smoothly, but in the unlikely event that it does not here are some problems which have been encountered:
Server will not start
This is usually due to a port conflict. Check that the Presence server was shut down properly. Is there an existing process called "PresenceServer.exe" in the Task Manager processes list? If so, right click it and select "End Process Tree" and try again.
One common port that causes conflict is the Channel Manager web application, which by default runs on port 8081. This can be changed in the presenceconfig.xml file.
Database will not start
If the database was not shut down cleanly (e.g. if the server was switched off) it is possible for the transaction log file (.wal) to become inconsistent with the main database file. In this case, try replacing the database with the backed up version (see above).
If you continue to encounter problems, please Email us or phone (321) 726 9941 (US) or 0208 972 1390 (UK).