Moving an application to production

These are the reasons why you might want to move applications, or part of their content, from one Infor d/EPM business applications installation to another Infor d/EPM business applications installation.
  • To move applications to production after you have completed testing the development environment.
  • To move applications to a different farm. For example, to test a new version of Infor d/EPM.
  • To move applications from a development single tenant to a production single tenant. Some operations require the assistance of Cloud Ops because of the upload limit of 128 MB.

This table describes the tasks for moving an application:

Completed Task Additional information
❑ Export and import OLAP data roles.

You must import the OLAP data roles into the production application before you import the OLAP data.

 Data Roles dashboard

See Exporting data roles and Importing data roles.
❑ Export and import application roles.

You must import the application roles into the production application before you import the OLAP data.

 Application Roles dashboard

See Exporting application roles and Importing application roles.
❑ Add custom data connections.

Custom data connections that are used by Application Studio reports are moved with the report export/import.

Data connections for OLAP mappings and so on must be recreated earlier.

 Data Connections dashboard

See Adding a data connection.
❑ Export and import mappings. Mappings Overview dashboard

See Exporting mappings and Importing mappings.
❑ Export and import OLAP data.

Typically, you do not transport OLAP data from development to production because the data is mostly in production.

However, you may need to move OLAP data from production to development in order to develop custom reports using real data.

 Databases dashboard

See Exporting and importing OLAP databases.
❑ Export and import queries and tables. Relational Modeling dashboard

See Exporting a model and Importing a model.
❑ Export and import customized reports. Application Studio

See Exporting, importing, and printing.
❑ Backup and restore the Designer and Integration databases. Microsoft SQL Server

See the Microsoft SQL Server documentation.

Cloud Ops must complete this task for single tenant installations.
❑ Update the tblSystemProperties table for the Designer database. Use SQL Server Management Studio to clear the values these fields:
  • FarmOLAP
  • FarmProfileName
  • COSAPM
  • COSProject

After clearing the values, start Designer and register the database repository.

See Registering a Designer database.

Cloud Ops must complete this task for single tenant installations.
❑ Export and import custom processes. Application Engine Process Editor

See Exporting processes to folder and Importing processes from folder.
❑ Export and import custom dashboards.

See Exporting dashboards and Importing dashboards.
❑ Export and copy ImportMaster definitions (IMD). Requires the ImportMaster full client.

See the ImportMaster online help.