mromy 2005/04/29 11:24:07 CEST
Modified files:
html README.html
Added files:
html README_4_0_6.html
Log:
- added upgrade readme for 4.0.6
- updated readme upgrade for 4.1
Revision Changes Path
1.2 +24 -9 jahia_update/html/README.html
http://jahia.mine.nu:8080/cgi-bin/cvsweb.cgi/jahia_update/html/README.html.diff?r1=1.1&r2=1.2&f=h
1.1 +196 -0 jahia_update/html/README_4_0_6.html (new)
http://jahia.mine.nu:8080/cgi-bin/cvsweb.cgi/jahia_update/html/README_4_0_6.html?rev=1.1&content-type=text/plain
Index: README_4_0_6.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.0.6 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.0.6 README file</h1>
<p>This is the README file for the Jahia Update from 4.0.5 to
4.0.6</p>
<h2 class="red">!!! This patch can only be applied to Jahia 4.0.5
!!!</h2>
<p>Before applying this patch, 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>
If you are using <strong>MySQL 4.0.x</strong> database with Jahia, be
sure to check the <a href="#2">
MySQL additional information</a> part of this document, it contains
some specific information and SQL scripts
that you will have to apply to your Jahia database for the update to
be completed.
<br/><br/>
<br/>
<h2>Upgrade procedure</h2>
<p><strong>1) Copy the JahiaUpdate_4_0_6.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.</strong> </p>
<p><strong>3) To start the upgrading process, type on the command
line:</strong></p>
<p class="code"> java -jar JahiaUpdate_4_0_6.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_5".
</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_5. If you have a
commercial license key
, just delete the newly copied license.xml file
located in <p
class="code">[install_path]/tomcat/webapps/jahia/WEB-INF/etc/config</p>and
rename
the previous license file to license.xml. <br/><br/>
</p>
<p><strong>4) After applying the patch, you need to remove the
following old libraries:</strong></p>
<p class="code">
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/jtds-0.5.1.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/mysql.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/oracle.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/poi-textextractionpatch.jar
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/postgresql-7.4.1-jdbc3.jar
</p>
<p><strong>5) 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>MySQL additional information</h2>
If you are using <strong>MySQL 4.0.x</strong> database, you need to
apply two sets of SQL commands to
alter the format of some tables. These changes are partly required if
you want to upgrade in the future
to <strong>MySQL 4.1.x</strong>, and also to extend the size of some
fields which may reveal too limited in some
cases.<br/>
You will first need to connect to your database (either in command
line or with a third party client) with a
user who has at least "alter" permission on the database. You can
then execute the following commands :<br/>
<p class="code">
ALTER TABLE jahia_grp_prop MODIFY name_jahia_grp_prop
varchar(150);<br/>
ALTER TABLE jahia_link MODIFY left_oid varchar(100);<br/>
ALTER TABLE jahia_link MODIFY right_oid varchar(100);<br/>
ALTER TABLE jahia_link MODIFY type varchar(100);<br/>
ALTER TABLE jahia_pages_def_prop MODIFY value_pages_def_prop
varchar(200);<br/>
ALTER TABLE jahia_pages_prop MODIFY prop_name varchar(150);<br/>
ALTER TABLE jahia_pages_prop MODIFY language_code
varchar(20);<br/>
ALTER TABLE jahia_slide_branches MODIFY uri varchar(200);<br/>
ALTER TABLE jahia_slide_branches MODIFY slidens varchar(50);<br/>
ALTER TABLE jahia_slide_children MODIFY uri varchar(200);<br/>
ALTER TABLE jahia_slide_children MODIFY slidens varchar(50);<br/>
ALTER TABLE jahia_slide_label MODIFY uri varchar(200);<br/>
ALTER TABLE jahia_slide_label MODIFY slidens varchar(50);<br/>
ALTER TABLE jahia_slide_links MODIFY linkto varchar(200);<br/>
ALTER TABLE jahia_slide_links MODIFY slidens varchar(50);<br/>
ALTER TABLE jahia_slide_latestrev MODIFY uri varchar(200);<br/>
ALTER TABLE jahia_slide_latestrev MODIFY slidens varchar(50);<br/>
ALTER TABLE jahia_slide_locks MODIFY object varchar(200);<br/>
ALTER TABLE jahia_slide_locks MODIFY slidens varchar(50);<br/>
ALTER TABLE jahia_slide_objects MODIFY uri varchar(200);<br/>
ALTER TABLE jahia_slide_objects MODIFY slidens varchar(50);<br/>
ALTER TABLE jahia_slide_permissions MODIFY object
varchar(200);<br/>
ALTER TABLE jahia_slide_permissions MODIFY slidens
varchar(50);<br/>
ALTER TABLE jahia_slide_property MODIFY uri varchar(200);<br/>
ALTER TABLE jahia_slide_property MODIFY slidens varchar(50);<br/>
ALTER TABLE jahia_slide_revision MODIFY uri varchar(200);<br/>
ALTER TABLE jahia_slide_revision MODIFY slidens varchar(50);<br/>
ALTER TABLE jahia_slide_revisions MODIFY uri varchar(200);<br/>
ALTER TABLE jahia_slide_revisions MODIFY slidens varchar(50);<br/>
ALTER TABLE jahia_slide_workingrev MODIFY uri varchar(200);<br/>
ALTER TABLE jahia_slide_workingrev MODIFY slidens
varchar(50);<br/>
ALTER TABLE jahia_user_prop MODIFY name_jahia_user_prop
varchar(150);<br/>
</p>
<br/>
This set of SQL commands reduces the size of some fields to prevent
problem that may occur when upgrading
from MySQL 4.0.x to MySQL 4.1.<br/>
<p class="code">
Script pour changer la taille des mediumInt � INT
</p>
This set of SQL commands extends the maxium length of integer fields
to allow for longer numbers.<br/>
A <a href="mysql_script.sql">SQL script file</a> is also provided
with all the SQL commands listed above.
<br/>
<br/>
<br/>
<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 Change Log</a> and
the <a href="http://www.jahia.org/readme">Jahia 4.0.6
README</a>.</p><br/>
<h2>File configuration modifications and optimizations</h2>
<p>Users with a custom configuration (e.g. LDAP; HTML Editors;....)
or users who 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_404_to_405/index.html">jahia config
files</a> - 20.4KB - online (files in folder jahia\WEB-INF\etc)
</li>
<li>
<a href="diff_jahiaconf_404_to_405.zip">jahia config
files</a> - 20.8KB - zip file (files in folder jahia\WEB-INF\etc)
</li>
<li>
<a href="diff_jahia_404_to_405/index.html">all jahia
files</a> - 1.52MB - online (files in folder jahia)
</li>
<li>
<a href="diff_jahia_404_to_405.zip">all jahia files</a> -
18.2mB - zip file (files in folder jahia)
</li>
</ul>
<p> </p>
</div>
<div class="footer">
Copyright 2004, <a href="http://www.jahia.org">Jahia Ltd</a> - All
rights reserved
</div>
</div>
</body>
</html>
Index: README.html
===================================================================
RCS file: /cvs/jahia_update/html/README.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README.html 28 Apr 2005 09:15:17 -0000 1.1
+++ README.html 29 Apr 2005 09:24:07 -0000 1.2
@@ -2,7 +2,7 @@
<!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 Readme</title>
+<title>Jahia 4.1 Readme</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<style type="text/css">
<!--
@@ -56,7 +56,7 @@
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 to <a href="#2">
+ 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/>
@@ -90,9 +90,24 @@
<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/XXXXX.jar<br/>
- </p>
+
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/commons-beanutils.jar
+
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/commons-codec-1.1.jar
+
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/commons-collections.jar
+
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/commons-digester.jar
+
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/commons-httpclient.jar
+ [install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/commons-lang.jar
+
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/commons-logging.jar
+
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/commons-validator.jar
+ [install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/jakarta-oro.jar
+ [install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/jdom.jar
+
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/slide-kernel-2.1-extractors.jar
+ [install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/slide-roles.jar
+ [install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/slide-stores.jar
+
[install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/struts-legacy.jar
+ [install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/struts.jar
+ [install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/webdav.jar
+ [install_path]/tomcat/webapps/jahia/WEB-INF/lib/dist/webdavlib.jar
+ </p>
<p><strong>5) Migrating your webapps/portlets:</strong></p>
<p>This tool only upgrades the Jahia CMS and Portal Server. If you
also want to upgrade the
@@ -142,14 +157,14 @@
You can then re-issue the previous "SHOW TABLE STATUS" command to
ensure the tables are now of the correct type.
<br/><br/>
Another way to ensure that the tables will be created in the correct
format during the upgrade process is to change
- the default settings of MySQL in the configuration file
(my.cnf/my.ini) file to set the default type for new tables
- to InnoDB. <br/>
+ 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. <br/>
Edit the my.cnf(linux) or my.ini(windows) and add the following line
in the [mysqld] part of the file :<br/>
<p class="code">
default-table-type=InnoDB
</p>
- Then restart your MySQL instance. New tables will now be created by
default in InnoDB format. You can now
- launch the jahia upgrade tool.<br/><br/>
+ 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>
If you have problems installing this update, check the Install
mailing
list (<a
href="http://www.jahia.org/install_list">http://www.jahia.org/install_list</a>).