Importing a Repository application component package in an on-premise installation

When you import the Repository application component package, the project, the underlying models, and all locked Application Roles will be overwritten:

When overwriting the Application Roles, the user assignments of the Application Roles remain untouched, as they are not part of the locked role definition.
When overwriting an Application Studio report catalog, the settings of the report catalog remain untouched, as they are not part of this application component. The report catalog settings are delivered by the Application Studio application component.

Note: The import of the Repository application component package will not affect reports and dashboards of the project. Only the project's models and Application Roles will be affected.

To import a Repository application component package in an on-premise installation:

Right-click the Projects folder in the tree and select Import Project.... A dialog opens in which you select the project sub-package file.
Navigate to the import folder and select the import file. To show the existing import files, select the file type Application Component (*.app_project) from the drop-down list. Default import file name: <Name of the Project>.app_project.
Click Open. The Import Conflict dialog opens. This dialog allows to resolve conflicts that happen when an object of the Repository application component to be imported already exists with the same name in the target repository project. You can either cancel the import or select an action to resolve the conflict:

Import object with new name

If an object, repository model, or Application Role, with the same name already exists in the target repository, the dialog prompts you to specify a new name for the object to import.

Overwrite existing object

If you select this option, an existing object in the target repository will be overwritten with the new one. If an existing object with the same name is detected, the dialog prompts you to decide whether to overwrite the target object or not import the Repository application component object. The dialog prompts you for each detected object that has an identical name in the target project. In these cases, the option Do not import the object is enabled.

Do not import the object

If you select this option, the object will not be imported. The option is enabled, if an existing object, repository model or Application Role with the same name is detected in the target repository project.

Always perform selected action

If you select this check box in combination with the option Overwrite existing object, existing objects in the target repository that have the same name will always be overwritten.

The action that you perform here applies to repository models and Application Roles as well.

If you click Cancel, the import is cancelled completely.
To start the import process, click OK.
Repository models and Application Roles are imported. The result of the Repository application component package import is a new or replaced project version respectively a previous project version that has been overwritten. The import will not apply object locks or other application meta data.