Page Comparison

Anchor
top top

This topic describes the steps necessary to upgrade your local XperienCentral development installation to a new version. After the upgrade, your website will remain unchanged and the newer version of XperienCentral will be in place. Upgrading an XperienCentral installation can be accomplished using the zip archive (GX_XperienCentral_x.x_SDK.zip), where x.x represents the version you are upgrading to.

 

Upgrading XperienCentral 

...

1. If you are working on a server compare the resulting repository.xml with the repository.xml on the server (in the /work/jcr folder) and merge the changes into the repository.xml on the server. Then open the /work/jcr/repository/workspaces/wm9/workspace.xml file on the server and replace the content of the <Workspace name="x"> tag with the one you find in the <Workspace name="x"> tag of the repository.xml file.
   1. You can skip the next two steps.
2. Open a Command prompt and navigate to the root folder of the newer version of XperienCentral.
3. Execute this command to build the JCR:
   
   mvn -s settings.xml -P configure-jcr-repository
   
   
4. Open the file <XperienCentral root>\upgrade.txt in the new directory.
5. Make all configuration changes that are listed for upgrading from your specific previous version of XperienCentral to the newer version.
   
   
6. Open a Command prompt and navigate to the root folder of the newer version of XperienCentral.

7. Execute the following command to build the new version of XperienCentral.

   mvn -s settings.xml -P build-project clean package
   
   

8. Copy the file Webmanager-webapps/Webmanager-backend-webapp/target/XperienCentral-backend-webapp-1.0-SNAPSHOT/WEB-INF/siteworks/configuration.xml from the old installation to the same directory in the new installation.
   
   

Copy the following directories containing all Media Repository, Who-is-Who, Product Catalog uploads as well as Flash files from the old installation of XperienCentral to the same location in the new project directory:

Webmanager-webapps/Webmanager-static-webapp/target/Webmanager-static-webapp-1.0-SNAPSHOT/cfg/*
Webmanager-webapps/Webmanager-static-webapp/target/Webmanager-static-webapp-1.0-SNAPSHOT/upload_mm/*
Webmanager-webapps/Webmanager-static-webapp/target/Webmanager-static-webapp-1.0-SNAPSHOT/upload/*

1. If the Who is Who or Product Catalog uploads are not stored in subdirectories of the webmanager-webapps/webmanager-static-webapp/target/Webmanager-static-webapp-1.0-SNAPSHOT/upload directory, copy the directories where they are stored to the same location in the new installation.

...

1. Start the Tomcat server (Apache-tomcat\bin\startup.bat). XperienCentral will perform the following tasks during the initial startup of the upgraded version:
   
   Upgrade services — a series of upgrade tasks are run. You will see messages similar to the following in the log file.
   Rebuild the JCR index — A In versions R27 and lower of XperienCentral, a new JCR index will be generated. For large websites, this may take some time.
   
   

2. Start the XperienCentral Setup Tool and log in.

3. Configure the contentindex_queue_reindex_schedule setting in the "application_settings" section on the General Tab in the Setup Tool to ensure that a reindex will be executed.
   
   

   Note
   The All accounts from the old version of XperienCentral are carried over to the upgraded version.

   
   

...

1. Check whether /web/setup shows the correct configuration.
2. Check whether the STARTUP_SETTINGS on the [General configuration] tab are correct.
3. Check whether the CENTRAL DATABASE SETTINGS and DATABASE CONNECTIONS on the [Database configuration] tab still refer to the correct databases.
4. Test the Edit environment and the public website.
5. In the Workspace, navigate to Configuration > Channel Configuration and ensure that the settings are configured the way you want them.
6. Restart XperienCentral if prompted to do so.

Your version of XperienCentral is now successfully upgraded.

 

Back to Top