OpenText™ Web Experience Management Motion: Release Notes

By default, items marked as system items are ignored. This prevents migrations from changing these items (for instance, replace WEM 10.5 DPM Page content type with an older version).

WEM Motion now supports installation in architectures with multiple CDS per stage

The offline connector is not compatible with the offline packages from previous WEM Motion versions. However, both WEM Motion versions can be maintained simultaneously for a period of time where the old backups are still necessary.

WEM Motion now supports migration of the following Object Types:

References between Content Instance and Content Instance Pages are now taken into account.

Migrations can now be done to and from WEM 16.

Content can be migrated to delivery directly, maintaining the publishing status. This feature only works for versions 10.5 or later and is dependent on the installation of a cumulative patch for WEM. Please contact OpenText™ support if you intend on using this feature.

Connectors now have a health endpoint that can be used for monitoring. The engine interface will also provide information about the connection with connectors.

Motion now includes a set of pre-configured navigators that expose existing WEM content tree.

WEM Motion can send an email report at the end of each job execution.

Since WEM Motion 2.5, besides Migration Jobs, there are also Deletion, Comparison, Computation and Script Jobs.

Since WEM Motion 2.5, it is possible to audit / trace all changes in WEM Motion, as well as migrated items.

Since WEM Motion 2.6.0 migrations can now be done to and from WEM 16.2.

Since WEM Motion 2.6.2 migrations can now be done to and from WEM 16.2.

The installation process has been revised. It has a much simpler installation process. Offering different architecture configurations that greatly reduce the complexity.

Option to install a single connector that communicates with every stage CDS in a WEM instance.

In WEM Motion 1.x, there was a different binary for each WEM version but from version 2.0 and onward the same binary can be used to connect to any WEM Version.

For both engine and connector it is now possible to install the software as a standalone process. Deploy to tomcat is still supported for both cases.

It is now possible to abort a job and resume it from the same point afterwards.

Transformation scripts now offer a jQuery like syntax.

Content is now moved between environments using streaming which greatly reduces the connectors memory footprint.

The computation is now faster with a significant reduction in the memory footprint. Improved conflict resolution policies during computation cycle.

The interface has been revamped, maintaining a similar UX. There is now only one web interface in the engine allowing you to navigate any connector configured.