Difference between revisions of "Upgrading Presence"

From PresenceWiki
Jump to: navigation, search
(See Also)
(See Also)
Line 69: Line 69:
If you continue to encounter problems, please [mailto:support@presencebpm.com Email us] or phone (321) 726 9941 (US) or 0844 770 4596 (UK).
If you continue to encounter problems, please [mailto:support@presencebpm.com Email us] or phone (321) 726 9941 (US) or 0844 770 4596 (UK).
==== See Also ====
=== See Also ===
* [[Presence Migration Guide]]
* [[Presence Migration Guide]]
* [[presenceconfig.xml]]
* [[presenceconfig.xml]]
* [[Installation]] Guide
* [[Installation]] Guide

Revision as of 07:45, 9 February 2010


This document describes best procedures for upgrading to Presence 3.5.5 from an earlier version.

Presence 3.5.5 uses the Sun 1.6 JRE, where as previous versions used the 1.5 JRE. For this reason some extra care should be taken to ensure compatibility with JDBC drivers, etc.

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

Disable Presence

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:


Database Backup

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 to a separate drive. Note that this can only be done if the database service is stopped (see above).

Run Installer

For instructions, refer to the Installation Guide.

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 1.6 JRE.

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.

Upgrade Complete

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 0844 770 4596 (UK).

See Also