Portal data import

Note

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.

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.