This document contains information that is important to note when upgrading to iSymphony 3.1 release candidate 1. Please be sure to completely read the information before upgrading.

Known Issues

Be sure to read the known issues section of the changelog. 

Loss of Settings

Although we try to make every change backwards-compatible, in some cases the effort involved in that is simply impractical. When upgrading from iSymphony 3.0 to iSymphony 3.1 release candidate 1, take note of the following:

• The permission overhaul has changed the architecture of the permissions system significantly. Unfortunately, because of the complexity of the system and the number of potential edge cases that may be missed, we are not able to copy existing permission definitions over from the architecture used in version 3.0. As a result, all permissions defined in version 3.0 will be cleared upon upgrade, and when the upgrade is complete, no permissions will be defined. This means that you will need to redefine your permissions after upgrading. With the improvements to the batch editing, this should be significantly quicker and easier to do with version 3.1 than version 3.0. Note that this also includes access rules for extension directories, so on upgrade, all extension directories will be public by default.
• The existing queue widgets have been removed, and since significantly fewer total widgets are typically necessary with the new widget, we have elected to allow users to reconfigure their dashboards as they see fit. Therefore, all existing queue widgets will be removed from dashboards, and the new widget must be added back and configured as necessary. 

Other Notes

• Please note that as previously announced, iSymphony 3.1 drops support for Java 6. If you are running Java 6, you will need to upgrade to Oracle Java 7 or above. See the Supported Platforms page for more details. 

Upgrade Steps

Follow these steps to upgrade iSymphony 3.x to iSymphony 3.1 RC 1:

1. Back up the entire /opt/isymphony3 directory before proceeding further. This is extremely important. 
2. Download the beta package that corresponds to your original installation method (see Determine the Installation Method for more details). The installation packages can be found in our Downloads Archive, under the Version 3 Development Builds header. 

3. Follow the RPM or Tarball upgrade instructions to install your server. See Upgrading iSymphony for more details.

   The Automated upgrade method cannot be used for beta upgrades.

Additional Upgrade Steps for Remote Agents

We have made significant improvements to our communication system in 3.1 RC 1. As a result, the method of specifying the broker for remote agents has changed. If you are using iSymphony with a remote agent, you must follow these additional steps to properly reconfigure the remote agent. Please note that these changes only need to be done on the remote agent, not on the main iSymphony server. 

1. Ensure the iSymphony remote agent is not running, by shutting down the iSymphony server on the remote agent machine. See Starting And Stopping The iSymphony Server for more details.

2. Edit the file /opt/isymphony3/server/jvm.args. Add a new line to the end with the following content:

   /opt/isymphony3/server/jvm.args

   -Dcom.xmlnamespace.panel.framework.jms.broker_url=tcp://<hostname>:<portname>

   Note the following:

   1. Change the <hostname> placeholder to the hostname or IP address of your primary iSymphony server.
   2. Change the <portname> placeholder to the port number that your primary iSymphony server is configured to set up its broker on. By default, this port is 51000. 
3. Save and close the file, and start the iSymphony remote agent.