Page Comparison

This topic describes how to upgrade a single XperienCentral server in a production environment as well as in a clustered environment.

...

In This Topic

...

Upgrading XperienCentral on a Single Server

...

First, a new deploy needs to be created. This is typically done by the software developer. See Creating 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 most cases this is not necessary. This usually only happens 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.

Process the Deploy for a

...

New configuration.xml

• Perform the steps as described in section How to Process the Deploy.

For most upgrades, you will not receive a new configuration.xml file. If you do receive a new configuration.xml file from GX Software, the system administrator must perform the following tasks:

1. Make a backup copy of <webmanager-root>\configuration\configuration.xml.
2. Copy the new configuration.xml over the old one in <webmanager-root>\configuration\.

...

Back to top 

...

Upgrading XperienCentral in a Clustered Environment

Upgrading XperienCentral in a clustered production environment is very similar to upgrading a standalone version of XperienCentral except that there are multiple instances of XperienCentral that must be upgraded (masterread/write node(s) and one or more slavesread-only nodes) and these must be upgraded in a specific order. To upgrade a clustered XperienCentral deployment, follow these steps:

1. Stop XperienCentral on all slave machinesread-only nodes.
2. Stop XperienCentral on the masterread/write node(s).

3. Upgrade XperienCentral first on

   the master

   one of the read/write node(s) and

   all slaves by following the steps in the previous section.Refer to the upgrade.txt file, located in the root directory of your XperienCentral installation,

   after successfully starting XperienCentral on that node, upgrade the remaining read/write and read-only nodes.

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

1. Start XperienCentral on a master server read/write node with the setting
   
   -Dwebmanager.clustering.filestore=false.
   
   XperienCentral is completely started when the following messages appears in the Tomcat log:
   

   <date><time>.gx.webmanager.startup.impl.Startup start
INFO: XperienCentral started successfully in x ms



2. When you have determined that the upgrade was successful, stop the masterread/write node.

3. On the master read/write node that you started and confirmed that the upgrade was successful in the steps above, change the setting clustering.filestore to true
   (-Dwebmanager.clustering.filestore=true).

4. Start XperienCentral on that masterread/write node.
   
   After the master read/write node is started, the file store will be initialized by the File Distribution Service (files from the upload and upload_mm directories). Depending on the number of/size of files on the website, this process could take some time. During this process, the server node is available for use but could be slower due to the impact from the file synchronization process. Editors should be able to continue working. The following message appears in the log when the File Distribution Service has completed its task:

   INFO: Finished scanning the web roots for files for the File Distribution Service



5. Start XperienCentral on the second master read/write noder if you are running a dual master read/write node environment. In a dual master environment, wait Wait until the second master read/write node has started successfully before starting XperienCentral on all slavesread-only nodes. This could also take some time because the second master 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 master read/write node will not be available for use.

6. In a single master read/write node environment, start XperienCentral on all slavesread-only nodes.

...

Environments that Do Not Use the File Distribution Service

1. Start XperienCentral on the master serverread/write node. XperienCentral is completely started when the following messages appears in the Tomcat log
   
   <date><time> nl.gx.webmanager.startup.impl.Startup start
INFO: XperienCentral started successfully in x ms
   
   
2. Confirm that the upgrade was successful.
3. Start XperienCentral on all slaves.

...

1. read-only nodes.

Back to top