Export de données (en vue d'une migration)

XML Export engine quick documentation.
--------------------------------------

Jahia 4.0 now introduces on-the-fly XML content export. This functionality
gives direct access to content stored in a Jahia system for sharing with
external systems. This feature will be extended in the future to also allow
import of XML data as Jahia content, but for the moment we will cover the
export feature that is already implemented.

In order to have the right to use this feature, you must be logged in as a
user that is a member of the "administrators" group for the site on which
you want to perform the XML extraction.

Here is a quick demonstration of an XML extraction of Jahia content.

1. Log in with a user that has site administration rights (such as your
super user account for example)

2. In your browser go to your default site by using the usual URL :

http://localhost:8080/jahia/Jahia

3. Now let's try exporting the default site completely in XML. In order
to do this you must modify the above URL to look like this :

http://localhost:8080/jahia/Jahia/pid/1/engineName/xmlsource?mode=site

If you get an error when processing this URL it might be because the
page "1" no longer exists in your system. Replacing the "1" with an
existing page number will do the trick.

If this succeeded you should see in your browser an XML document (with
Mozilla use the "View page source" if the content is displayed weird) that
contains all the ACTIVE content of the site. Here is an example of output
of this XML export :

<?xml version="1.0" encoding="UTF-8" ?>
<jahia>
<contentSite name="myjahiasite" title="My Jahia Site">
<contentPage type="direct">
<titles>
<title language="fr">page1</title>
<title language="en">Home</title>
</titles>
<direct>

<contentField name="logo" type="org.jahia.services.fields.ContentFileField" shared="true">
<entry language="en" workflowState="1" versionID="1043243004">
<file url="images/jahia_logo.gif"/>
</entry>
</contentField>
<contentField name="footerText" type="org.jahia.services.fields.ContentBigTextField" shared="true">
<entry language="en" workflowState="1" versionID="1043243004"> <![CDATA[ 2002, Jahia Ltd - All rights reserved ]]>
</entry>

</contentField>
</direct>
</contentPage>
</contentSite>
</jahia>

Now you may want to export just a page, just a container list, a container or
a single field. In order to do this we present here the syntax for the URL in
more detail. Basically the "mode" specifies the type of object we want to
extract. In order to extract an object in XML, we must give the identifier of
that object. This is done before the "mode" parameter in the URL. You are
probably already familiar with the "pid" argument which specifies the page
identifier. But first let's present the different mode accepted values :

.../engineName/xmlsource?mode=site
.../engineName/xmlsource?mode=page
.../engineName/xmlsource?mode=containerlist
.../engineName/xmlsource?mode=container
.../engineName/xmlsource?mode=field

Now here are the identifier names for the different content objects :

.../site/myjahiasite/engineName/xmlsource?mode=site
.../pid/1/engineName/xmlsource?mode=page
.../clid/1/engineName/xmlsource?mode=containerlist
.../cid/1/engineName/xmlsource?mode=container
.../fid/1/engineName/xmlsource?mode=field

The identifier values for objects can be obtainer by clicking on on of the
properties buttons on a content object. Note that once again these XML
extractions will only work on ACTIVE content. So if the object hasn't been
activated it cannot be exported.

Also some fields have special behavior. Bigtexts fields are stored in files
in Jahia, but are exported as CDATA text in XML exports. Also File fields are
for the moment exported as BASE64 data included within the XML export, which
might make the resulting XML a bit large. In a future version of the engine
we will provide another mode that will just export links to the actual content.

Le résultat est bien un fichier zip contenant tout

Jahia version4.2.1_01, Build19612

1. export.properties
   
2. archive zip qui contient:
   
   • categories.xml
     
   • export_fr.xml
     
   • fileacl.xml
     
   • dossier shared
     
   • site.properties
     
   • dossier users
     
   • users.xml
     
   • templates.jar qui contient:
     
     1. templates.xml
        
     2. dossier des templates du site
        
     3. classes.jar
     
     

Second point, ayant créé une page en "Jahia 4.2.1" je ne la voie pas, une fois l'import en 5.0.5 effectué .... je vois bien l'utilisateur créé et je peux le modifier. Ayant renommé un template il apparait également, seule la page créé n'est pas trouvé aprés l'import ... est-ce normal ?