September 12-14, 2018 Raleigh, NC

Migration – Moving From 4 to 5 Evan Culler Software Developer

Overview How to migrate Best Practices Differences Between 4 and 5 Demo Q&A

How To Migrate Informer 4 Packages Add Informer 4 entities you want to migrate to an Informer 4 package Download the package Drag into an Informer 5 web page

Recommended Import Processes Report Migration Why use this approach? Best for a slower transition with thorough testing Allows users to continue to work in i4 while migrating to i5 Have users tag reports they use with a Migration tag Package tagged reports and import them If a user misses a report they can add the tag and generate a new download link for the package When importing a package with reports that have already been imported Informer 5 only keeps the report that was updated most recently.

Recommended Import Processes Datasource Import Why use this approach? Have all of your mappings, fields, and links ready to go Gives you a chance to optimize reports for i5 Don’t use if… Your Informer 4 instance has a lot of mapped tables and fields that you won’t be reporting off of Add datasources you use for reporting to an i4 package Build new reports or use Informer 4 as a reference to build reports

Recommended Import Processes Combined Approach Why use this approach? You want all mapped tables, properties and links to migrate and you also want to migrate specific reports. Start with a datasource migration outlined in the previous slide Then use the Report migration approach to bring over any reports you would like bring.

New Informer New Approach Optimizations to handle larger queries Leverage New Technologies Post query filtering Consolidate reports by selecting more data and applying post query filters Example: Report A selects orders from 1997 Report b selects orders from 1998 Create a report that selects orders from 1997 and 1998 and create separate filters for 1997 and 1998

New Informer New Approach I5 to I4 Parity Currently there are still some features in 4 that have not been implemented in 5 and will not migrate. We will continue updating migration to support these features as they are added Mappings Suites, Code Files, and Queries with Sub Selects Security Informer 5 has implemented a new security model that is not compatible with Informer 4s. Users and Groups will migrate but the security associated with them will not

Identifying Migration Candidates Informer 4 Launch Audit Check what reports are being run Informer 4 Derby Package Provides useful reports on Informer 4’s metadata

Questions?