Infos
Official Jahia Web Site.
Access to the complete source code, bug tracking system, development mailing list, software documentation and much more.

- Jahia Change Log

Jahia Upgrade 4.1.1_01 README file

This is the README file for the Jahia Update 4.1.1_01

Status

This release mainly improves features like file management and clustering, as well as fix a few bugs. We also implemented support for Single Sign-On (SSO) methods with CAS library to offer SSO between different Java applications, and with JCIFS library for NTLM authentication.

New features/improvements in 4.1.1


Please check the complete change Log to view a complete list of all the modifications.

This patch can be applied either to Jahia 4.0.6, 4.0.7, Jahia 4.1.0 or 4.1.0_01. It will upgrade your Jahia installation 4.1.1_01.


Upgrade procedure

Before applying this upgrade, it is highly recommended to proceed to a backup of your data (database + files on disk), especially if you are patching a production server.

Please note that because of the type of actions processed during the update from 4.0.6 or 4.0.7 (addition and modification of tables in database, copy of db content), the update tool may, in some case, not work correctly, especially when using database MySQL 4.0.x. Please be sure to check the upgrade issues part of this document before proceeding to the upgrade if you are using MySQL database and are upgrading from Jahia 4.0.6.

If upgrading from Jahia 4.0.6, your original license key may not work with this release. If you have acquired a commercial license or if you are using a non-trial key and if your are entitled to this upgrade , please send an e-mail with your current license key to license@jahia.org to request an updated license key.
The trial key bundled with this upgrade will anyway work for 60 days without limitation.

1) Copy the JahiaUpdate4.1.1_01.jar file to the following directory:

[install_path]/tomcat/webapps/jahia

2) Make sure tomcat is stopped and that the database is running and available (excepted for the embedded Hypersonic database, which is the database used by Jahia by default).

Under Unix/Linux, make sure that you are running the patch under the same user that is running Jahia, you may otherwise encounter some directories permissions issues.

3) To start the upgrading process, type on the command line:

java -jar JahiaUpdate4.1.1_01.jar

It will first display a warning message to make sure you have stopped Jahia. If everything is ok, press "y" to proceed.

The process will pause after each step of the upgrade. It will ask if you wish to apply the next patch. Press "Y" to confirm.

A message will then be displayed to inform you if the update was successfull. A backup of all modified files has also been made during the process. All these backup files end with "_4_0_x" (respectively "_4_1_x" if you upgraded from Jahia 4.1.0).

The update process will also copy a new trial key (license.xml) file, but will rename your existing license file to license.xml_4_0_6 ( respectively "license.xml_4_1_0" if you upgraded from Jahia 4.1.0).

4) After applying the upgrade


5) Upgrading the default templates:

The Jahia upgrade tool will not upgrade your set of templates or the default corporate portal templates, but no changes are required to run with Jahia 4.1. However if you wish to benefit from correction made to the corporate portal templates (for example the blog template), you will need to update to the latest version of the. you can check the diffs in the corporate templates cvs manually.

6) Migrating your webapps/portlets:

This tool only upgrades the Jahia CMS and Portal Server. If you also want to upgrade the standalone webapps prepackaged with Jahia to their latest version, please refer to this page:

http://projects.jahia.org/migrationguide.html

Warning: This upgrade process is optional and not directly linked with this Jahia kernel upgrade. You may perfectly keep your current webapps versions. Webapps prepackaged with Jahia or other portlets you may have developed or integrated are standalone seperate web applications.


Upgrade issues with MySQL if upgrading from Jahia 4.0.6

Please read carefully this part as it contains needed information to alter the settings of the MySQL database to allow the upgrade tool to complete successfully

If you are using MySQL database, the upgrade tool will also need to ensure that some new tables that are created during the process are in a certain table type, namely InnoDB. If you are using MySQL 4.1, there should not be any problems as new tables are created by default in InnoDB format. However, with MySQL 4.0 default table format is MyISAM. During the upgrade process, the tool will try to change this type as it creates the new tables, however in some cases we noticed that the command has no effect.

The best way to ensure that the tables will be created in the correct format during the upgrade process is to change the settings of MySQL in the configuration file (my.cnf/my.ini) to set the default type for new tables to InnoDB before executing the upgrade tool.
Edit the my.cnf(Unix/Linux) or my.ini(windows) and add the following line in the [mysqld] part of the file :

default-table-type=InnoDB

Once you restart your MySQL server, new tables will be created by default in InnoDB format.

If your database server runs under Unix/Linux, you also need to change a default setting to allow case-insensitive SQL requests. Under Windows and MacOSX, case-insensitive SQL requests are activated by default, but not under Linux, so you need to edit the my.cnf configuration file of MySQL and add the following statement in the [mysqld] part of the file :

lower_case_table_names=1

Then restart your MySQL instance. You can now launch the jahia upgrade tool.

To check if the new tables (all tables beginning with "jahia_sl2") were correctly created in InnoDB, issue the following sql command once logged into you MySQL database :

SHOW TABLE STATUS FROM your_database LIKE 'jahia_sl2%';


This should display the status of all tables beginning with "jahia_sl2". The column "Type" will give you the current format of the tables.
If the type is "InnoDB", then the upgrade tool has been able to successfully alter the table format. If however the type is still "MyISAM" for whatever reason, you will need to change manually the format of all "jahia_sl2" tables by issuing the following SQL commands :

ALTER TABLE jahia_sl2_uri type=innodb;
ALTER TABLE jahia_sl2_object type=innodb;
ALTER TABLE jahia_sl2_binding type=innodb;
ALTER TABLE jahia_sl2_parent_binding type=innodb;
ALTER TABLE jahia_sl2_links type=innodb;
ALTER TABLE jahia_sl2_locks type=innodb;
ALTER TABLE jahia_sl2_branch type=innodb;
ALTER TABLE jahia_sl2_label type=innodb;
ALTER TABLE jahia_sl2_version type=innodb;
ALTER TABLE jahia_sl2_version_history type=innodb;
ALTER TABLE jahia_sl2_version_preds type=innodb;
ALTER TABLE jahia_sl2_version_labels type=innodb;
ALTER TABLE jahia_sl2_properties type=innodb;
ALTER TABLE jahia_sl2_permissions type=innodb;


You can then re-issue the previous "SHOW TABLE STATUS" command to ensure the tables are now of the correct type.


Upgrading to MySQL 4.1.x

If you plan to upgrade at the same time from MySQL 4.0 to MySQL 4.1, you should be aware that MySQL stores data in Latin1" character encoding, whereas MySQL 4.1.x leaves you the choice at installation time to either use Latin1 or UTF8. We strongly recommend that you install MySQL 4.1.x in Latin1 character enconding if you want to migrate your date from MySQL 4.0, as we found no easy way to upgrade from a MySQL 4.0.x Latin1 database to a MySQL 4.1.x UTF8 database without encountering problems with accentuated or special characters.
Please check this page of the MySQL website for more information regarding migrating to MySQL 4.1.x.

The following improvements have been made:

To get the complete list, please consult the Jahia 4.1 changelog and the Jahia 4.1 README.


Copyright 2005, Jahia Ltd - All rights reserved