eXo Platform 3.5

## Chapter 8. Upgrade eXo Platform

Upgrading eXo Platform from 3.0 to 3.5 is generally a procedure which includes 2 steps:

Step 1. Upgrade the project extensions.

Step 2. Upgrade the project and the product data.

This chapter aims at instructing you how to archive Step 1 via the following topics:

- Prerequisites

  Questions that help developers to gather all requirements for their upgraded project, required preparations of an extension project, and steps which need to be adpated in eXo Platform.

- Update Maven dependencies, configurations and components

  How to update Maven dependencies, configurations and components.

- Update extensions

  How to update your custom eXo Platform extensions, including updating Kernel XML Schema, portal and APIs.

### Note

Upgrading data can be strongly dependent on both your deployments and environments, so it is recommended that you contact http://support.exoplatform.com to bootstrap the Step 2.

## 8.1. Prerequisites

Before upgrading, you first need to understand how to create a project which is based on eXo Platform 3.5. For more details, refer to Create Your Own Portal.

And now, you need to gather all requirements for your upgraded project by clarifying the following questions:

- Do you actually need to migrate your project sources?

- Have you created any new portal containers in your system?

- Have you made any lifetime-related changes on eXo Platform? Would you like to keep these changes?

- Have you developed a custom application? Where have you stored your application data?

- Have you configured a dedicated JCR workspace?

- Which eXo APIs are you using in your code?

- Have you overridden any files of eXo Platform?

- Have you disabled any services of eXo Platform?

- Which Kernel configurations have you customized?

Prepare for your extension project

You need to create a new branch for eXo Platform 3.5 extension project, then clone your source code of eXo Platform 3.0 with that of eXo Platform 3.5.

The way to package your project customization called extensions has been introduced in eXo Platform 3.0. Therefore, by using the WAR extension configuration approach, you can overload eXo Platform's default files defined in WARs, such as gtmpl, favicon, xml, jsp. For more details on how to create your extension project, refer to the Create Your Own Portal section.

Because there are not any changes on the eXo Platform 3.5 extension mechanism, your extensions should be mostly compatible. However, if your extension was overriding either of the eXo Platform 3.0 built-in files, you should check that the file has not been changed in eXo Platform 3.5 and update it if any.

What needs to be adapted in eXo Platform extension

There are 4 main steps which need to be defined for updating eXo Platform extension from 3.0 to 3.5:

- Update your project Maven dependencies in the POM files.

- Update your eXo Platform 3.5 configurations.

- Update components in your eXo Platform extension to use components of Platform 3.5

- Update your eXo Platform extension which are customised features/components (were added new/ modified/ delete in eXo Platform 3.0 extension), and make sure they can work well in eXo Platform 3.5 environment.

`See also`

- Update Maven dependencies, configurations and components

- Update extensions

## 8.2. Update Maven dependencies, configurations and components

After gathering all requirements, and preparing for your extension project and adaptions in eXo Platform extension, you then need to update:

- Maven dependencies

- Configurations

- Components

Maven dependencies

eXo Platform includes many components, so if you want to update your eXo Platform extension to use eXo Platform 3.5, you need to update the version of all dependencies in the POM files, and select the version of dependencies which are compatible with eXo Platform 3.5. For example, eXo Platform 3.5.1 needs to have the following main dependencies:

    <!-- kernel -->

    <dependency>

        <groupId>org.exoplatform.kernel</groupId>

        <artifactId>kernel-parent</artifactId>

        <version>2.3.5-GA</version>

    </dependency>

    <!-- core -->

    <dependency>

       <groupId>org.exoplatform.core</groupId>

       <artifactId>core-parent</artifactId>

       <version>2.4.5-GA</version>

    </dependency>

    <!-- ws -->

    <dependency>

       <groupId>org.exoplatform.ws</groupId>

       <artifactId>ws-parent</artifactId>

       <version>2.2.5-GA</version>

    </dependency>

    <!-- jcr -->

    <dependency>

      <groupId>org.exoplatform.jcr</groupId>

      <artifactId>jcr-parent</artifactId>

      <version>1.14.5-GA</version>

    </dependency>

    <!-- jcr service -->

    <dependency>

      <groupId>org.exoplatform</groupId>

      <artifactId>exo-jcr-services</artifactId>

      <version>1.14.5-GA</version>

    </dependency>

    <!-- commons -->

    <dependency>

      <groupId>org.exoplatform.commons</groupId>

      <artifactId>exo.platform.commons</artifactId>

      <version>1.1.5</version>

    </dependency>

    <!-- exogtn -->

    <dependency>

       <groupId>org.exoplatform.portal</groupId>

       <artifactId>exo.portal.parent</artifactId>

       <version>3.2.2-PLF</version>

    </dependency>

    <!-- webos -->

    <dependency>

      <groupId>org.exoplatform.webos</groupId>

      <artifactId>webos-parent</artifactId>

      <version>2.0.2</version>

    </dependency>

    <!-- ecms -->

    <dependency>

      <groupId>org.exoplatform.ecms</groupId>

      <artifactId>exo-ecms</artifactId>

      <version>2.3.5</version>

    </dependency>

    <!-- ide -->

    <dependency>

       <groupId>org.exoplatform.ide</groupId>

       <artifactId>exo-ide-parent</artifactId>

       <version>1.1.4</version>

    </dependency>

    <!-- cs -->

    <dependency>

      <groupId>org.exoplatform.cs</groupId>

      <artifactId>cs</artifactId>

      <version>2.2.7</version>

    </dependency>

    <!-- ks -->

    <dependency>

      <groupId>org.exoplatform.ks</groupId>

      <artifactId>ks</artifactId>

      <version>2.2.7</version>

    </dependency>

    <!-- social -->

    <dependency>

      <groupId>org.exoplatform.social</groupId>

      <artifactId>social-project</artifactId>

      <version>1.2.7</version>

    </dependency>

    <!-- integration -->

    <dependency>

      <groupId>org.exoplatform.integration</groupId>

      <artifactId>integ</artifactId>

      <version>1.0.5</version>

    </dependency>

Configurations

After updating Maven dependencies, you need to update configurations via answering 2 questions:

- In your eXo Platform extension, did you override anything in $PLATFORM_TOMCAT_HOME/gatein/conf?

  - If NO, you can skip this step, and simply keep all configurations in $PLATFORM_TOMCAT_HOME/gatein/conf.

  - If YES, you first need to keep all configurations of eXo Platform 3.5, then define which configurations you want to add/remove/update. After that, you can put them into $PLATFORM_TOMCAT_HOME/gatein/conf.

### Note

There are some new configurations in $PLATFORM_TOMCAT_HOME/gatein/conf/ which are related to how to deploy the eXo Platform clustering, and JBoss Cache configuration.

- In your eXo Platform extension, did you override anything in $PLATFORM_TOMCAT_HOME/bin?

  - If NO, you can skip this step, and simply keep all configurations in $PLATFORM_TOMCAT_HOME/bin.

  - If YES, you first need to keep all eXo Platform 3.5's origin configurations, then add/remove/update your extension configuration into it.

### Note

$PLATFORM-TOMCAT-HOME/bin/gatein.sh and $PLATFORM_TOMCAT_HOME/bin/gatein.bat are no longer used. Therefore, you should add your customized configurations in a more official way to set environment variables via setenv.sh or setenv.bat.

Components

There are many components in eXo Platform, so if you update your eXo Platform extension to eXo Platform 3.5, you need to update the version of all eXo Platform 3.5's components. To do so, simply configure the Maven POM file that allows you to use the artifacts (eXo Platform 3.5 and its components). For more details, see the Update project Maven dependencies section. All eXo Platform 3.5's components will be automatically included in your eXo Platform extension.

There are some new components in eXo Platform 3.5 that have not been existing in eXo Platform 3.0, including Webos, Wiki, and Gadget-pack. To use these components, simply activate their profiles. For more details, see the Profiles of eXo Platform section.

In eXo Platform 3.5, the "intranet" portal is defined in the acme-intranet.war file (not in the office-portal.war file of eXo Platform 3.0). So if you have overridden anything in the "intranet" portal, you need to synchronize your extension with the acme-intranet.war file of eXo Platform-3.5.

`See also`

- Prerequisites

- Update extensions

## 8.3. Update extensions

The next procedure of upgrading eXo Platform is to update your custom eXo Platform extensions, including:

- Kernel XML Schema

- Portal

- APIs

Kernel XML Schema

- Simply upgrade the version from kernel_1_0.xsd to kernel_1_2.xsd in all .xml configurations files.

    <configuration xmlns="http://www.exoplatform.org/xml/ns/kernel_1_2.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.exoplatform.org/xml/ns/kernel_1_2.xsd http://www.exoplatform.org/xml/ns/kernel_1_2.xsd">

        .....

    </configuration>

Portal

- Portal data import

### Note

It is recommended you have the knowledge of the import mechanism by referring to the Data Import Strategy section.

Processing the portal data import includes the following tasks:

- Improve the current data import strategy so that it becomes more flexible in various scenarios.

- Deploy an extension after you have initialized the portal that allows the extension to contribute its entities to an existing site.

- Reimport data by overwriting an existing entire configuration at each startup.

What's new?

Previous behavior | New behavior
--- | ---
The previous mode for navigations is defined using the overridden configuration. Merge: Merge data from the XML descriptor to the existing data. Override: Destroy any existing data, and create new ones. The previous mode has two main issues: The behavior for instance disables the "always merge data" usecase. It means that it is always impossible to merge new navigations nodes from XML to MOP. The behavior is configured by the overridden parameter. | The new behavior which is configured at the import level with a field parameter would have the following values: conserve: Import data. However, if the navigation has been existing, it will be kept. insert: Insert the missing descriptor data by adding new nodes without any modifications on the existing nodes. merge: Merge the descriptor data, add missing nodes and update the nodes of the same name. overwrite: Always destroy the previous data and create new ones.

For example, if you want to merge the new portal navigation from the configuration file and the existing portal navigation into the current eXo Platform, you can configure as below:

    <object-param>

      <name>portal.configuration</name>

      <object type="org.exoplatform.portal.config.NewPortalConfig">

        <field name="predefinedOwner">

         <collection type="java.util.HashSet">

           <value><string>classic</string></value>

         </collection>

        </field>

        <field name="ownerType">

          <string>portal</string>

        </field>

        <field name="templateLocation">

          <string>war:/conf/portal</string>

        </field>

        <field name="importMode">

          <string>merge</string>

        </field>

      </object>

    </object-param>

### Note

When a mode is not specified, the default mode will be conserve.

- Authentication: eXo Platform 3.5 uses a new authentication mechanism so-called the WCI authentication mechanism. This change from GateIn into the WCI module is because:

  - Authentication is commonly part of Java EE and happens at the Servlet Container layer, while WCI is the layer of integration between our stack and the Servlet Container.

  - WCI provides an easier integration of SSO providers that allows the SSO module to depend on the WCI module instead of integrating directly with the GateIn module. Its main benefit is to improve the quality of SSO and to decouple SSO from GateIn.

  - The GateIn stack wants to support and leverage specifications of both Servlet 3.0 and Servlet 2.5 that are not supported by the GateIn module. Meanwhile, WCI can serve both.

  - The Servlet 3.0 provides a programmatic login feature which can be used to implement WCI.

  - WCI provides the stronger guaranty of the authentication quality, meanwhile the authentication of GateIn was not unit tested. By moving the GateIn to WCI module, the test can be made against several implementations.

If there are other new portal containers in your eXo Platform extension, you need to update the authentication mechanism in the $PLATFORM-TOMCAT-HOME/conf/jaas.conf file. For example, in case you have added a new portal container named "company" to eXo Platform, you need to configure the new authentication module for the new portal container as follows:

    <!--this configuration for defaul portal container with name "portal"-->
    gatein-domain {
      org.gatein.wci.security.WCILoginModule optional;
      org.exoplatform.services.security.jaas.SharedStateLoginModule required;
      org.exoplatform.services.security.j2ee.TomcatLoginModule required;
    };

    <!--this configuration for new portal container with name "company"-->
    gatein-domain-company {
      org.gatein.wci.security.WCILoginModule optional
        portalContainerName="company"
      	realmName="gatein-domain-company";
      org.exoplatform.services.security.jaas.SharedStateLoginModule required
        portalContainerName="company"
      	realmName="gatein-domain-company";
      org.exoplatform.services.security.j2ee.TomcatLoginModule required
        portalContainerName="company"
      	realmName="gatein-domain-company";
    };

For more details, see the Change the JAAS realm section.

APIs

eXo Platform 3.5 has many changes on the data model and APIs. Therefore, if there are any new customized components in your eXo Platform extension that use eXo Platform 3.0 APIs, you need to check if they can work well in eXo Platform 3.5 or not. For more details, see the eXo Platform 3.5 APIs section.

Finally, you need to update your customized components if needed.

`See also`

- Prerequisites

- Update Maven dependencies, configurations and components

Copyright © 2009-2012. All rights reserved. eXo Platform SAS