Skip to content

Upgrading from MDW 5.5

Jump to bottom
donaldoakes edited this page Nov 11, 2016 · 15 revisions

1. Container

TODO

2. Database

RDBMS

For runtime state persistence MDW 6 uses a relational database (MySQL, MariaDB or Oracle), just like MDW 5.5. However, document storage has been externalized in MDW 6 and so a data conversion step is needed for in-flight workflow continuation. Execute this upgrade script to update the data model and migrate document data: /master/mdw/database/mysql/upgrade_from_mdw55.sql.

MongoDB

A key advantage of MDW 6 is the option to use a special-purpose document store instead of the old RDBMS CLOB technique. In the absence of any MongoDB configuration in mdw.properties, MDW will store document values as CLOBS in the column DOCUMENT_CONTENT.CONTENT. This is convenient in situations like local development where you may not wish to install MongoDB. If you have MongoDB, you can set mdw.mongodb.host and mdw.mongodb.port, to tell MDW to use this docstore option.

3. Java

  • MDW 6 requires Java 1.8, so update your Tomcat Runtime Environment in Eclipse if it's on something older.
    Also change your Gradle or Maven build configuration and Eclipse JRE and project facets to use Java 1.8.
  • Many Java packages and classes from mdw-common have been renamed from MDW 5.5 to streamline the code and more accurately represent its purpose. You can use Eclipse refactoring and "Organize Imports" to lessen the pain of changing your code to reference these renamed resources.

4. Configuration

  • To indicate development mode, previously you set the system property -DruntimeEnv=dev in your Tomcat startup config. For MDW 6 this system property changes to -Dmdw.runtime.env=dev
  • Web access is now controlled by access.yaml. As a starting point you can copy this from here: /master/mdw/config/access.yaml.
    Then remove mdw.dev.user from your mdw.properties and instead set devUser in access.yaml.

5. Custom Web

  • JSF customization is no longer supported in MDW 6. Custom web assets under mdw-hub should use the HTML5/AngularJS extensibility techniques. If your MDW 5.5 project includes mdw-admin package customization, this package should be renamed to mdw-hub to take effect in MDW 6.

6. Designer

  • For full MDW 6 support in Designer, upgrade to the latest published version (currently 8.9.9).
Clone this wiki locally