Although DMM requirements depend on the application that is leveraging the engine, some common needs must be addressed on each installation.
Each application’s specific requirements will be detailed in the section for that application in the manual.
DMM requires the setup of two database connections, one for the source of the data and the other for the destination of the data. The following table describes the required permissions for the connection depending on the supporting database technology and on the migration role.
Alternatively you can use DMM with the Runtime Connection (this is the way in the OutSystems Cloud PaaS), which for the Migration functionality that requires 2 connections means you have to setup 2 instances of DMM (in the Origin and Destination environments) and either:
In the DMM Settings setup a REST connection type in the Destination environment to the Source environment (that has the DMM REST API setting enabled)
Do an Export in the Source followed by an Import in the Destination.
Requires Read Permissions on the following tables
OSSYS_APP_DEFINITION_MODULE
OSSYS_APPLICATION
OSSYS_DBCATALOG
OSSYS_ENTITY
OSSYS_ENTITY_ATTR
OSSYS_ENTITY_RECORD
OSSYS_ESPACE
OSSYS_ESPACE_VERSION
OSSYS_EXTENSION
OSSYS_GROUP
OSSYS_GROUP_ROLE
OSSYS_GROUP_USER
OSSYS_MODULE
OSSYS_ROLE
OSSYS_USER
OSSYS_USER_ROLE
OSSYS_TENANT
OSSYS_SOLUTION
OSSYS_SEGMENTATIONKIND
OSSYS_CALLBACK
OSSYS_BASIC_TYPE
OSSYS_MODULE
OSSYS_MOBILE_PLATFORM
OSSYS_EXTENSION
OSSYS_MODULE_KIND
OSSYS_EXTENSION_VERSION
OSSYS_APPLICATION_ICON
OSSYS_SITE_PROPERTY_DEFINITION
OSUSR_*
OSSYS_BPM_ACTIVITY **
OSSYS_BPM_ACTIVITY_OUTPUT **
OSSYS_BPM_PROCESS **
OSSYS_BPM_PROCESS_INPUT **
OSSYS_BPM_PROCESS_OUTPUT **
OSSYS_BPM_PROCESS_DEFINITION **
OSSYS_BPM_PROCESS_INPUT_DEF **
OSSYS_BPM_PROCESS_OUTPUT_DEF **
OSSYS_BPM_ACTIVITY_DEFINITION **
OSSYS_BPM_ACTIVITY_OUTPUT_DEF **
OSSYS_BPM_PROCESS_STATUS **
OSSYS_BPM_ACTIVITY_STATUS **
OSEVT_* **
OSSYS_EMAIL ***
OSSYS_EMAIL_CONTENT ***
OSSYS_EMAIL_STATUS ***
OSSYS_EMAIL_DEFINITION ***
OSSYS_EMAIL_STATUS_LABEL ***
OSSYS_SITE_PROPERTY_DEFINITION ****
OSSYS_SITE_PROPERTY ****
OSSYS_SITE_PROPERTY_SHARED ****
* for all tables that will be target of migration
** when migrating BPT data
*** when migrating emails data
**** when migrating Site Properties
Requires Read Permissions on the following tables
OSSYS_APP_DEFINITION_MODULE
OSSYS_APPLICATION
OSSYS_DBCATALOG
OSSYS_ENTITY
OSSYS_ENTITY_ATTR
OSSYS_ENTITY_RECORD
OSSYS_ESPACE
OSSYS_ESPACE_VERSION
OSSYS_EXTENSION
OSSYS_ROLE
OSSYS_MODULE
OSSYS_TENANT
OSSYS_SOLUTION
OSSYS_SEGMENTATIONKIND
OSSYS_CALLBACK
OSSYS_BASIC_TYPE
OSSYS_MODULE
OSSYS_MOBILE_PLATFORM
OSSYS_BPM_PROCESS_DEFINITION **
OSSYS_BPM_PROCESS_INPUT_DEF **
OSSYS_BPM_PROCESS_OUTPUT_DEF **
OSSYS_BPM_ACTIVITY_DEFINITION **
OSSYS_BPM_ACTIVITY_OUTPUT_DEF **
OSSYS_BPM_PROCESS_STATUS **
OSSYS_BPM_ACTIVITY_STATUS **
OSSYS_EMAIL_DEFINITION ***
OSSYS_EMAIL_STATUS_LABEL ***
Requires Read and Write Permissions on the following tables
OSSYS_GROUP
OSSYS_GROUP_ROLE
OSSYS_GROUP_USER
OSSYS_USER
OSSYS_USER_ROLE
OSSYS_MODULE_KIND
OSSYS_EXTENSION_VERSION
OSSYS_APPLICATION_ICON
OSSYS_SITE_PROPERTY_DEFINITION
OSSYS_BPM_ACTIVITY **
OSSYS_BPM_ACTIVITY_OUTPUT **
OSSYS_BPM_PROCESS **
OSSYS_BPM_PROCESS_INPUT **
OSSYS_BPM_PROCESS_OUTPUT **
OSEVT_* **
OSSYS_EMAIL ***
OSSYS_EMAIL_CONTENT ***
OSSYS_EMAIL_STATUS ***
OSSYS_SITE_PROPERTY_DEFINITION ****
OSSYS_SITE_PROPERTY ****
OSSYS_SITE_PROPERTY_SHARED ****
Requires Read, Write and Alter permissions on the following tables
OSUSR_*
* for all tables that will be target of migration
** when migrating BPT data
*** when migrating emails data
**** when migrating Site Properties
When using Data Append Mode or Runtime Connection the Alter table permission is not required.
Requires SELECT grant on the following tables
OSSYS_APP_DEFINITION_MODULE
OSSYS_APPLICATION
OSSYS_DBCATALOG
OSSYS_ENTITY
OSSYS_ENTITY_ATTR
OSSYS_ENTITY_RECORD
OSSYS_ESPACE
OSSYS_ESPACE_VERSION
OSSYS_EXTENSION
OSSYS_GROUP
OSSYS_GROUP_ROLE
OSSYS_GROUP_USER
OSSYS_MODULE
OSSYS_ROLE
OSSYS_USER
OSSYS_USER_ROLE
OSSYS_TENANT
OSSYS_MODULE_KIND
OSSYS_EXTENSION_VERSION
OSSYS_APPLICATION_ICON
OSSYS_SITE_PROPERTY_DEFINITION
OSUSR_*
OSSYS_BPM_ACTIVITY **
OSSYS_BPM_ACTIVITY_OUTPUT **
OSSYS_BPM_PROCESS **
OSSYS_BPM_PROCESS_INPUT **
OSSYS_BPM_PROCESS_OUTPUT **
OSSYS_BPM_PROCESS_DEFINITION **
OSSYS_BPM_PROCESS_INPUT_DEF **
OSSYS_BPM_PROCESS_OUTPUT_DEF **
OSSYS_BPM_ACTIVITY_DEFINITION **
OSSYS_BPM_ACTIVITY_OUTPUT_DEF **
OSSYS_BPM_PROCESS_STATUS **
OSSYS_BPM_ACTIVITY_STATUS **
OSEVT_* **
OSSYS_EMAIL ***
OSSYS_EMAIL_CONTENT ***
OSSYS_EMAIL_STATUS ***
OSSYS_EMAIL_DEFINITION ***
OSSYS_EMAIL_STATUS_LABEL ***
OSSYS_SITE_PROPERTY_DEFINITION ****
OSSYS_SITE_PROPERTY ****
OSSYS_SITE_PROPERTY_SHARED ****
* for all tables that will be target of migration
** when migrating BPT data
*** when migrating emails data
**** when migrating Site Properties
Requires SELECT grant on the following tables
OSSYS_APP_DEFINITION_MODULE
OSSYS_APPLICATION
OSSYS_DBCATALOG
OSSYS_ENTITY
OSSYS_ENTITY_ATTR
OSSYS_ENTITY_RECORD
OSSYS_ESPACE
OSSYS_ESPACE_VERSION
OSSYS_EXTENSION
OSSYS_ROLE
OSSYS_MODULE
OSSYS_TENANT
OSSYS_BPM_PROCESS_DEFINITION **
OSSYS_BPM_PROCESS_INPUT_DEF **
OSSYS_BPM_PROCESS_OUTPUT_DEF **
OSSYS_BPM_ACTIVITY_DEFINITION **
OSSYS_BPM_ACTIVITY_OUTPUT_DEF **
OSSYS_BPM_PROCESS_STATUS **
OSSYS_BPM_ACTIVITY_STATUS **
OSSYS_EMAIL_DEFINITION ***
OSSYS_EMAIL_STATUS_LABEL ***
Requires SELECT, UPDATE, INSERT and DELETE grant on the following tables
OSSYS_GROUP
OSSYS_GROUP_ROLE
OSSYS_GROUP_USER
OSSYS_USER
OSSYS_USER_ROLE
OSSYS_MODULE_KIND
OSSYS_EXTENSION_VERSION
OSSYS_APPLICATION_ICON
OSSYS_SITE_PROPERTY_DEFINITION
OSUSR_*
OSSYS_BPM_ACTIVITY **
OSSYS_BPM_ACTIVITY_OUTPUT **
OSSYS_BPM_PROCESS **
OSSYS_BPM_PROCESS_INPUT **
OSSYS_BPM_PROCESS_OUTPUT **
OSEVT_* **
OSSYS_EMAIL ***
OSSYS_EMAIL_CONTENT ***
OSSYS_EMAIL_STATUS ***
OSSYS_SITE_PROPERTY_DEFINITION ****
OSSYS_SITE_PROPERTY ****
OSSYS_SITE_PROPERTY_SHARED ****
Requires Read and Alter permissions on the sequences:
OSSEQ_*
Requires Read permission on the ALL_SEQUENCES entity.
* for all tables that will be target of migration
** when migrating BPT data
*** when migrating emails data
**** when migrating Site Properties
The Alter sequence permission is not required when using Data Append Mode or Runtime Connection.
Internet access must be assured in the machine from which DMM is being executed - if that is not possible, DMM has workarounds to validate offline subscribing for example, so internet access is not a mandatory requisite.
DMM requires access to a couple of domains, and without this access, execution of migration scripts may be hindered:
This domain is used to activate, validate, and refresh your subscription for the product. There is an offline subscription manager but it is much simpler to handle the subscribing questions automatically from within DMM.
We capture some execution metrics to get statistical information and to help us continuously improve DMM.