...
First, a new deploy needs to be created. This is typically done by the software developer. See Create the Deploy and What to Deliver to the System Administrator for information on creating a deploy and what items to deliver to the system administrator. If it is necessary, you can request a new configuration.xml file . In but in most cases this is not necessary. This usually step is only happens necessary if you want to add new functional components that you don't already use. If you do receive a configuration.xml file from GX Software, deliver it to the system administrator. Contact GX Software to receive a new configuration.xml file.
...
In most XperienCentral deployments, a number of the properties in the various configuration files are customized for each specific environment. During an upgrade, these files should not be overwritten. Instead, you should perform a diff to determine what the differences are between the files delivered by GX Software and those already present in your customized environment. In some releases, new properties are introduced which you must pick up in your configuration file(s). If no new properties have been introduced in a configuration file between releases, you can use it the current version of the file in the upgraded version as is.
The files to check for every release are listed below. Other files in an XperienCentral can also be modified in a release and they those changes are always specifically described in the Upgrade Notes.
...
After receiving the files from the developer, the system administrator performs the following tasks to process the deploy and the configuration.xml (if applicable):
- Make If necessary, make a backup copy of
/vol/www.mywebsite/configuration.xml. - Replace If necessary, replace the old copy of of
configuration.xmlwith the new version. - Perform the steps as described in Process the Deploy.
License Additions
Apart from the files as mentioned in in What to Deliver to the System Administrator, depending on your upgrade, you sometimes also have to deliver a new new configuration.xml file file depending on the circumstances surrounding your upgrade. Contact GX Software to receive a new new configuration.xml file.
...
- Stop XperienCentral on all read-only nodes.
- Stop XperienCentral on the read/write node(s).
Upgrade XperienCentral first on one of the read/write node(s) and after successfully starting XperienCentral on that single node, upgrade the remaining read/write and read-only nodes by following the steps in Upgrading XperienCentral on a Single Server.
- See Upgrade Notes per Version for further tasks (if any) that you need to perform for the newly installed version of XperienCentral.
...
Environments Using the File Distribution Service
- Start XperienCentral on a read/write noder with the setting
-Dwebmanager-clustering.filestore=false.
XperienCentral is completely started when the following messages appears in the Tomcat log:[Date] [Time] nl.gx.webmanager.startup.impl.Startup startINFO: XperienCentral started successfully in x ms - When you have determined that the upgrade was successful, stop the read/write node.
- On the read/write node that you started and confirmed that the upgrade was successful in the steps above, change the setting
clustering.filestoretotrue(-Dwebmanager.clustering.filestore=true). - Start XperienCentral on that read/write node.
...
- Start XperienCentral on the second read/write node if you are running a dual environment.
- In a dual read/write node environment, wait until the second read/write node has started successfully before starting XperienCentral on all read-only nodes. This could also take some time because the second read/write node needs to synchronize files from the central file store to the local disk. Until the file synchronization process is complete, the second read/write node will not be available for use.
- In a single read/write node environment, start XperienCentral on all read-only nodes.
...
Environments that Do Not Use the File Distribution Service
- Start XperienCentral on the read/write node. XperienCentral is completely started when the following messages appears in the Tomcat log:
26-jan-2010 13:05:35 nl.gx.webmanager.startup.impl.Startup startINFO: XperienCentral started successfully in x ms - Confirm that the upgrade was successful.
- Start XperienCentral one by one on all other read/write and read-only nodes.
...