pvollenweider 2005/05/04 10:07:51 CEST
Added files:
html README_4_1.html
Removed files:
html README.html
Log:
Rename 4.1 readme
Revision Changes Path
1.10 +0 -245 jahia_update/html/README.html (dead)
http://jahia.mine.nu:8080/cgi-bin/cvsweb.cgi/jahia_update/html/README.html?rev=1.9&content-type=text/plain
1.1 +245 -0 jahia_update/html/README_4_1.html (new)
http://jahia.mine.nu:8080/cgi-bin/cvsweb.cgi/jahia_update/html/README_4_1.html?rev=1.1&content-type=text/plain
Index: README_4_1.html
====================================================================
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";>
<head>
<title>Jahia 4.1 Readme</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<style type="text/css">
<!--
BODY { margin : 0px; background-color : #999999; color :
#000000; font-size : 10px; font-family : Verdana, Arial, Helvetica, sans-serif;
}
A { text-decoration : none; color : #006699; }
A:hover { text-decoration : underline;}
DIV.main { background-color : #FFFFFF; width : 768px; display :
block; }
DIV.header { background-color : #FFFFFF; border-bottom : 4px solid
#E7E7E7; width : 768px; }
DIV.header SPAN { border-bottom : 15px solid #006699; display : block; }
DIV.box { width : 190px; color : #666666; font-family : Arial,
Helvetica, sans-serif; float : left; margin : 10px; }
DIV.box .title { color : #ffffff; background-color : #006699; padding
: 2px 5px 2px 5px; white-space : nowrap; display : block; }
DIV.box .content { border-left : 1px solid #A8A8A8; border-right : 1px
solid #A8A8A8; border-bottom : 1px solid #A8A8A8; padding : 5px; margin-bottom
: 10px; background-color : #E7E7E7; }
DIV.maincontent { width : 540px; pading : 0 10px 0 10px;
background-color : #FFFFFF; float : left; margin-top : 10px; }
DIV.maincontent LI { padding-top : 10px; }
DIV.maincontent H1 { font-family : Arial, Helvetica, sans-serif; font-size
: 24px; color : #666666; }
DIV.maincontent H2 { font-family : Arial, Helvetica, sans-serif; font-size
: 14px; color : #999999; }
DIV.footer { border-top : 4px solid #006699; padding : 10px 0 10px
0; display : block; text-align : center; background-color : #FFFFFF; width :
768px; clear : both; }
DIV.maincontent .code { font-family : "Courier New", Courier, mono; font-size
: 11px; padding-left: 20px;}
DIV.maincontent .red { color : #B42C29; }
-->
</style>
</head>
<body>
<div class="header">
<span><img src="http://www.jahia.org/jahia_logo.gif"; width="100"
height="50" alt=""/></span>
</div>
<div class="main">
<div class="box">
<div class="title">Infos</div>
<div class="content">
<a href="http://www.jahia.org"; class="bold">Official Jahia Web
Site.</a><br/>
Access to the complete source code, bug tracking system,
development mailing list, software
documentation and much more.
<br/><br/>
- <a href="http://www.jahia.org/changelog";>Jahia Change Log</a>
</div>
</div>
<div class="maincontent">
<h1>Jahia Upgrade 4.1 README file</h1>
<p>This is the README file for the Jahia Update 4.1</p>
<h2 class="red">!!! This upgrade can only be applied to Jahia 4.0.6
!!!</h2>
<p>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.</p>
Please note that because of the type of actions processed during the
update (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 <strong>MySQL 4.0.x</strong>. Please
be sure to check the <a href="#2">
upgrade issues</a> part of this document before proceeding to the
upgrade if you are using
<strong>MySQL</strong> database with Jahia.
<br/><br/>
As this is an upgrade to a new release of Jahia (and not only a
patch), 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
<a href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a> to request
an updated license key. <br/>
The trial key bundled with this upgrade will work for 60 days without
limitation.<br/><br/>
<br/>
<h2>Upgrade procedure</h2>
<p><strong>1) Copy the JahiaUpdate_4_1.jar file to the following
directory:</strong></p>
<p class="code">[install_path]/tomcat/webapps/jahia</p>
<p><strong>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).<br/><br/> 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.</strong> </p>
<p><strong>3) To start the upgrading process, type on the command
line:</strong></p>
<p class="code"> java -jar JahiaUpdate_4_1.jar</p>
<p>
It will first display a warning message to make sure you have
stopped
Jahia. If everything is ok, press "y"
to proceed. The update tool will deploy some files and make
necessary changes to the database.
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_6".
</p>
<p>
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. <br/><br/>
</p>
<p><strong>4) After applying the upgrade, you need to remove the
following old libraries:</strong></p>
<p class="code">
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/commons-beanutils.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/commons-codec-1.1.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/commons-collections.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/commons-digester.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/commons-httpclient.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/commons-lang.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/commons-logging.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/commons-validator.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/jakarta-oro.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/jdom.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/slide-kernel-2.1-extractors.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/slide-roles.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/slide-stores.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/struts-legacy.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/struts.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/webdav.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/webdavlib.jar
</p>
<p><strong>5) Upgrading the default templates:</strong></p>
<p> The Jahia upgrade tool will not upgrade your set of templates or
the default corporate portal templates, but
should not require any changes to run with Jahia 4.1. If you
still wish to update to the latest version of the
templates, you will have to check the diffs in the
<a
href="http://cvspub.jahia.org/cgi-bin/cvsweb.cgi/corporate_portal_templates/?only_with_tag=JAHIA-4-1-BRANCH";
target="_blank">
corporate templates cvs</a> manually.
<p><strong>6) Migrating your webapps/portlets:</strong></p>
<p>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:<br/>
<br/>
<a
href="http://projects.jahia.org/migrationguide.html";>http://projects.jahia.org/migrationguide.html</a><br/>
<br/>
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.<br/>
</p>
<br/>
<a name="2"></a><h2>Upgrade issues with MySQL</h2>
<h2 class="red">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</h2>
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
<strong>InnoDB</strong>. If you are using
MySQL 4.1, there should not be any problems as new tables are created
by default in <strong>InnoDB</strong> format.
However, with MySQL 4.0 default table format is
<strong>MyISAM</strong>. 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.
<br/><br/>
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
(<em>my.cnf</em>/<em>my.ini</em>) to set the default type for new tables
to InnoDB before executing the upgrade tool. <br/>
Edit the <em>my.cnf</em>(linux) or <em>my.ini</em>(windows) and add
the following line in the [mysqld] part of the file :<br/>
<p class="code">
default-table-type=InnoDB
</p>
If your database server runs under <strong>Linux</strong>, you also
<span class="red"><strong>need</strong></span> 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
<em>my.cnf</em> configuration file of MySQL and add the following
statement in the [mysqld] part of the file :
<p class="code">
lower_case_table_names=1
</p>
Then restart your MySQL instance. You can now launch the jahia
upgrade tool. New tables will now be
created by default in InnoDB format. <br/><br/>
<p>
To check if the new tables (all tables beginning with "jahia_sl2")
are of the correct type, issue the following
sql command once logged into you MySQL database :<br/>
<br/>
<p class="code">SHOW TABLE STATUS FROM your_database LIKE
'jahia_sl2%';</p>
<br/>
This should display the status of all tables beginning with
"jahia_sl2". The column "Type" will give you the current format
of the tables. <br/>
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 : <br/>
<p class="code">
ALTER TABLE jahia_sl2_uri type=innodb;<br/>
ALTER TABLE jahia_sl2_object type=innodb;<br/>
ALTER TABLE jahia_sl2_binding type=innodb;<br/>
ALTER TABLE jahia_sl2_parent_binding type=innodb;<br/>
ALTER TABLE jahia_sl2_links type=innodb;<br/>
ALTER TABLE jahia_sl2_locks type=innodb;<br/>
ALTER TABLE jahia_sl2_branch type=innodb;<br/>
ALTER TABLE jahia_sl2_label type=innodb;<br/>
ALTER TABLE jahia_sl2_version type=innodb;<br/>
ALTER TABLE jahia_sl2_version_history type=innodb;<br/>
ALTER TABLE jahia_sl2_version_preds type=innodb;<br/>
ALTER TABLE jahia_sl2_version_labels type=innodb;<br/>
ALTER TABLE jahia_sl2_properties type=innodb;<br/>
ALTER TABLE jahia_sl2_permissions type=innodb; <br/>
</p>
<br/>
You can then re-issue the previous "SHOW TABLE STATUS" command to
ensure the tables are now of the correct type.
<br/><br/>
<br/>
<a name="3"></a><h2>Upgrading to MySQL 4.1.x</h2>
<p>
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 <strong>Latin1"</strong> character encoding, whereas MySQL 4.1.x
leaves you the choice at installation time to
either use <strong>Latin1</strong> or <strong>UTF8</strong>. We
strongly recommend that you install MySQL 4.1.x
in <strong>Latin1</strong> 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.<br/>
Please check <a
href="http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html";
target="_blank">this page</a> of
the MySQL website for more information regarding migrating to MySQL
4.1.x.<br/><br/>
</p>
<h2>The following improvements have been made:</h2>
<p>To get the complete list, please consult the <a
href="http://www.jahia.org/changelog";>Jahia 4.1 README</a>.<br/></p>
<br/>
<h2>File configuration modifications and optimizations</h2>
<p>Users with a custom configuration (e.g. LDAP; HTML Editors;....)
or users which performed some fine tunings
(e.g. Database connection pool) on their Jahia environement will have
to merge their modifications with the newly provided
configuration files.
The upgrade will indeed override your old configuration files with
the new Jahia default values. A diff of all the configuration
differences may be found here:</p>
<ul>
<li>
<a href="diff_jahiaconf_406_to_410/index.html">jahia config
files</a> - 70.9KB - online (files in folder jahia\WEB-INF\etc)
</li>
<li>
<a href="diff_jahiaconf_406_to_410.zip">jahia config
files</a> - 58.9KB - zip file (files in folder jahia\WEB-INF\etc)
</li>
<li>
<a href="diff_jahia_406_to_410/index.html">all jahia
files</a> - 1.39MB - online (files in folder jahia)
</li>
<li>
<a href="diff_jahia_406_to_410.zip">all jahia files</a> -
10.8MB - zip file (files in folder jahia)
</li>
<li>
<a
href="diff_corporate_portal_templates_460_to_410/index.html">Corporate portal
templates</a> - 225KB - online (files in folder jahia)
</li>
<li>
<a
href="diff_corporate_portal_templates_460_to_410.zip">Corporate portal
templates</a> - 68KB - zip file (files in folder jahia)
</li>
</ul>
<p> </p>
</div>
<div class="footer">
Copyright 2005, <a href="http://www.jahia.org";>Jahia Ltd</a> - All
rights reserved
</div>
</div>
</body>
</html>
![http://www.jahia.org/jahia_logo.gif"](http://www.jahia.org/jahia_logo.gif"){kind=link}