Upgrade from Jahia xCM 6.6.2 to DigitalFactory 7.0.0

This upgrade to the consists of 1 unique easy step, please read it carefully before proceeding.

Please make sure you don't have ongoing workflows on your platform before starting your migration
  • Stop the user requests / traffic to the server (either on the front-end Apache HTTPD server or firewall/router)
  • Stop Jahia before backing up and running the fix applier
  • Backup your Jahia installation before running the fix applier
  • Run a pre-production test first
For this upgrade you will need to upgrade to Tomcat 7, we are providing 2 Fix Applier :

For a standalone installation

Step 1:Jahia Core & Modules Migration

The first step of the migration is to copy the fix applier you would like to use on your production server.

At this stage, a list of all the files you have customized in your installation will help you to go through the upgrade and decide more easily if you want to merge, keep or overwrite the files.

For all the files impacted, the fix applier will create a backup in the following folder:

$USER_HOME/.fixapplier/backup/ and a detailed log is also available in your <Jahia_installation>/tomcat/webapps/ROOT/META-INF/updates/history/fixes/DigitalFactory7.0-package_6.6.2.0_r47118_to_7.0.0.0_r49489.log or if you didn't use the default ROOT context in your <Jahia_installation>/tomcat/webapps/<your context>/META-INF/updates/history/fixes/DigitalFactory7.0-package_6.6.2.0_r47118_to_7.0.0.0_r49489.log

If the fix creator detects that a file has been modified it will try to automatically merge it. If the merge fails you will be able to overwrite the files or skip it installing the modification.
If the merge fails or you decide to skip it, a diff file <file_name>.patch will be available in the destination folder, please make sure that you don't forget to manually apply the changes.

1. Stop Jahia

2a. If your are upgrading your complete Jahia package :

Open a terminal in the JAHIA_INSTALLATION/ and type the following command:

java -jar <PATH-TO-FIX-APPLIER>/DigitalFactory7.0-package_6.6.2.0_r47118_to_7.0.0.0_r49489.jar

If you use Digital Experience Manager's configuration externalization:


By default the FixApplier will try to look for an externalized configuration in the default location (tomcat/lib/jahia-config.jar). If you are not using the default location, you need to specify it on the FixApplier command line as in the following example:

 java -DalternateJahiaConfigPath=tomcat/jahiaConfig/org/jahia/config -jar DigitalFactory7.0-package_6.6.2.0_r47118_to_7.0.0.0_r49489.jar

In the above example the externalized configuration is inside an exploded directory tomcat/jahiaConfig. If you are using a JAR to store the externalized configuration (this is the default behavior), you need to specify the configuration location as in the next example:

 java -DalternateJahiaConfigPath=../../lib/jahia-config.jar!org/jahia/config -jar DigitalFactory7.0-package_6.6.2.0_r47118_to_7.0.0.0_r49489.jar

The "!" (exclamation point) is used to specify a path inside the JAR file.

If you are using Digital Experience Manager in a web context other than ROOT:


If you have installed Digital Experience Manager in another context than the default ROOT context, you will need to specify the directory location of the Digital Experience Manager web application on the file system in a command line option, as in the following example:

 java -DwebappDirectory=tomcat/webapps/jahia -jar -jar DigitalFactory7.0-package_6.6.2.0_r47118_to_7.0.0.0_r49489.jar

In the above example the "jahia" context has been used instead of the default ROOT context. Note that the web application could be located anywhere else, simply specify the directory in the command line property and the FixApplier will look for it in the specified directory.

2b. If you are upgrading of your webapps/ROOT :

Open a terminal in the JAHIA_INSTALLATION/tomcat/webapps/ROOT or JAHIA_INSTALLATION/tomcat/webapps/<your context> if you didn't use the default ROOT context  and type the following command:

java -jar <PATH-TO-FIX-APPLIER>/DigitalFactory7.0-package_6.6.2.0_r47118_to_7.0.0.0_r49489.jar

The fix applier will manage the upgrade of your platform by deleting, updating and merging all the necessary files. It will now handles the migration of Jahia Core and all the additional Jahia modules installed on your platform.

In case you have externalized your configuration (jar file or folder), you will need to apply the modification relative to jahia.properties and jahia.advanced.properties manually at the appropriate place.

Please review your log before starting the next step to ensure you haven't missed a file that needs to be manually merged.

3. Clean the following Tomcat folder

The fix applier now handles the cleaning of the tomcat folders automatically but depending on the OS and some permissions you may need to clean it manually.

Remove the content of your folders <JAHIA_INSTALLATION>/tomcat/temp and <JAHIA_INSTALLATION>/tomcat/work

4. Clean the ressource folder

The fix applier will also handles the cleaning of the /webapps/<your context>/resources folder automatically but depending on the OS and some permissions you may need to clean it manually.

Remove the content of your folder  <JAHIA_INSTALLATION>/tomcat/webapps/ROOT/resources or <JAHIA_INSTALLATION>/tomcat/webapps/<your context>/resources if you didn't use the default ROOT context.

5. Start JAHIA

At the end of the startup process, go to http://localhost:8080/tools/search.jsp and click on Repository re-indexing - Do repository re-indexing on the next Jahia start

6. Restart your JAHIA

Jahia will perform a complete re-indexation

Your upgrade to Jahia is now completed


Download these 2 fix appliers and follow the instructions on the left



Que vous soyez un utilisateur de Jahia ou bien intéressé par une évaluation de nos solutions, nous sommes ici pour vous aider.

Nous contacter

Partagez cette page