Moving an application to production

Often during the lifecycle of a project, you will need to move content to production after you have completed testing in the development environment. You can move content between different applications of the same tenant or from tenant to tenant.

You can move an implementation of Infor d/EPM business applications or a custom application.

When moving your implementation of Infor d/EPM business applications to another tenant, you transport some content between the Infor d/EPM business applications, and some content between custom applications, which hold your customizations and extensions. See the "Customizing restricted Infor applications" topic for information on which content resides in which application.

It is possible to move only parts of an application.

This table describes the tasks, in the order in which the task must be completed, for moving an application:


Completed		Additional information
❑	Create the target application. When moving content of a custom application the first time, you need to create a target application to which you want to import content. Select the same capabilities as in the source application when creating the application.	Applications dashboard See Managing applications.
❑	Add custom data connections that are used by Application Engineprocesses, Application Studio, and relational modeling. It is important to use the same unique names of data connections as in the source application. Custom data connections used by Application Studio reports are also moved with the report export/import.	Data Connections dashboard See Adding a data connection .
❑	Export and import load queries, scripts, and tables of the integration and staging relational databases. This task is needed if you want to move content to a different tenant. If you have a small dataset, you can include your data in the bundle. If you have large data sets, export only schema definitions and load queries. You should load the data later from the source.	Relational Modeling dashboard See Exporting a model and Importing a model.
❑	Export and import the business model. This is valid only for the Infor d/EPM business applications. If you are migrating a custom application, skip this task.	Business Modeling See Model management.
❑	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.
❑	IFS roles When transporting an application to another tenant, you need to verify that the target tenant has the needed IFS roles and users. Register IFS users and roles and assign them to OLAP data and application roles.	Users and User Groups dashboard See Registering IFS users and roles.
❑	Export and import the OLAP database. The OLAP database contains cubes, dimensions, subsets, rules, structure data and 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 OLAP mappings for your custom solution.	Mappings Overview dashboard See Exporting mappings and Importing mappings.
❑	Export and import custom Application Engine processes. These processes are located in your custom application.	Application Engine Process Editor See Exporting a process package and Importing a process package.
❑	Export and import customized reports. These reports are located in your custom application.	Application Studio See Exporting, importing and printing.
❑	Export and import custom dashboards. These dashboards are located in your custom application.	See Exporting dashboards and Importing dashboards.