Migrating CDE dashboards from Pentaho 4.x to 5.x

Thanks to Pedro Vale, head of the Webdetails group for writing this note in the redmine wiki

Migrating dashboards

1. Upload existing dashboards to PUC
2. If you're using widgets, upload the contents of /cde/widgets to /public/cde/widgets
3. For each widget, edit it and save its settings. This will update the widget metadata and make it consistent with 5.x
4. Restart the server or call the CDE cache refresh url (/pentaho/plugin/pentaho-cdf-dd/renderer/refresh).
5. For each dashboard using widgets, remove and readd the widget.
6. In the datasources section, please update your mondrian datasource references - Simply selecting them again from the drop down will make it work. Alternatively, you can enable the legacy fallback solutoin described below.

Ensuring mondrian datasource references continue working

Step 1: Enabling Thomas Morgner's legacy fallback solution (note: disabled by default)

1 - open /tomcat/webapps/pentaho/WEB-INF/classes/classic-engine.properties
2 - add the following line

mondrian.spi.CatalogLocator=org.pentaho.reporting.engine.classic.extensions.datasources.mondrian.LegacyCatalogLocator

Step 2: Create and populate a mappings properties file

1 - (if not exists) create /tomcat/webapps/pentaho/WEB-INF/classes/mondrian-schema-mapping.properties
2 - add the mappping for the intended mondrian catalog; the new 5.0 syntax for mondrian catalogs must abide by the rule:

mondrian:/

Two mapping examples:

Example 1:
 in /plugin-samples/cda/cdafiles/mondrian-jndi.cda you can see this datasource definition:

<datasources><datasources>
<connection id="1" type="mondrian.jndi">
<jndi>SampleData</jndi>
<catalog>SteelWheels</catalog>
<cube>SteelWheelsSales</cube>
</connection></datasources><connection id="1" type="mondrian.jndi"><cube></cube>
</connection>
</datasources>

(see catalog value)

to handle this case, we would set in mondrian-schema-mapping.properties:

SteelWheels=mondrian:/SteelWheels

Example 2:
in /plugin-samples/pentaho-cdf-dd/cde_samples1.cda you can see this datasource definition:

<datasources>
<connection id="mdxQuery" type="mondrian.jndi">
<catalog>../steel-wheels/analysis/steelwheels.mondrian.xml</catalog>
<jndi>SampleData</jndi>
</connection>
<connection id="sqlQuery" type="sql.jndi">
<jndi>SampleData</jndi>
</connection>
</datasources>

(see catalog value)

to handle this case, we would set in in mondrian-schema-mapping.properties:

steelwheels.mondrian.xml=mondrian:/SteelWheels

(disregard the path, mapping is done with the filename)