You can install the DMM OutSystems Component directly from the OutSystems Forge. Just follow the link below:

Infosistema DMM

DMM OutSystems frontend security access setup

You need to grant the role "DMMOperator" to users who want to access the DMM OutSystems frontend pages (we removed the "registered" option from those pages; these are business users you must set the role for, not lifetime users).  

You can give or verify the role in your OutSystems environment's standard user application at https://your-environment/users/ 

Setup Infosistema DMM OutSystems Component

After DMM installation, when you access the component (after login) there will be a link near the top of the DMM application for "Management > Settings" where you can set up your installation.

You can change the following settings inside the settings page:

Database Access Configuration

Without a doubt, this is the most important setting. It defines the database connections that will be available for the migration processes. An important note is that when you define a connection DMM only tests its connectivity. However, you must make sure the correct permissions are granted to those connections so the migration processes are executed flawlessly. The requirements are listed here.

When you set up a new connection you can pick if the database is Microsoft SQL Server, Oracle Database, or MySQL. After that initial choice, you can then fill the values that represent the connection. When you save the connection, a connectivity test is made to make sure DMM Component can connect to the specified database.

Note that MySQL is only available for data export or for the source of data migration, i.e. Infosistema DMM won't be able to insert or update data into MySQL instances.

Also note that although OutSystems may give you connection strings to their databases in the Cloud PaaS Environments, there may not be network connectivity between the OutSystems Cloud PaaS environments (you are able to access the databases with those connection strings from your onPrem servers, but not between OutSystems environments, for example when configuring DMM in the QA environment to access the PRD environment as source of data). If such access doesn't exist or isn't possible, you should use the Runtime Connection available.    

The Runtime Connection is always present and represents the database connection to the environment where Infosistema DMM is installed.

The options in the image below  (Request Secure Connection, Upload Secure Connection)  are a way DMM built and was used in the past to get a direct database connection in the OutSystems Cloud PaaS. DMM has this encrypted way for OutSystems to make a connection available to their customers in their Cloud PaaS, this was specifically useful when OutSystems clients needed to migrate data keeping the IDs (which is only possible when a direct database connection with enough privileges is available).

To the best of our knowledge, OutSystems is no longer supporting these types of connections, redirecting clients to use the Runtime Connection (which doesn't allow for the Primary Key Integrity, keeping the record IDs in a data migration), so you shouldn't use these options:

REST API Key

If you are for example in the OutSystems PaaS Cloud, and you do not have direct database access between the OutSystems environments you will have to use the Runtime Connection to access the data bases. In this situation, DMM offers the REST API Connection type for you to be able to execute the Data Migration functionality (as opposed to to an Export/Import in 2 separate actions).

To setup this type of connection you start by installing DMM in both the data origin and data destination environments.

Then on the data origin environment, under the settings menu option, you define the REST API KEY for the origin environment: 

After setting up the  REST API Key on the data origin environment (see imagens above), you can on the data destination environment setup a new connection of the  DMM REST type:

In the destination environment, when you are setting up the DMM REST connection (image directly above), you will define the parameters "DMM Server Url" and "ApiToken" equal to the parameters defined in the origin environment (under the menu option Settings, label  REST API KEY, as presented in the second image above).

Folder For Import/Export

Each time Infosistema DMM executes an Export/Import it saves information inside a file.

This setting defines the folder where the file is placed.

You should enter the full path of the folder and make sure that the OutSystems IIS user has “read” and “write” access to that folder.

If you are on the OutSystems PaaS Cloud, you should setup the path:  D:\User\InfosistemaDMM

Proxy Server Information

Infosistema DMM needs an internet connection for license validation and to collect some execution indicators for Infosistema. If your installation lies behind a proxy, you can set up the proxy information in this setting by providing the corresponding host, username, and password.

Activating and licensing your installation

After installation, DMM Component is ready to execute migrations under the Free Tier. However, to prevent abuse of the product, we require that you activate your installation, otherwise you will be limited to five executions of the engine. 

The Free Tier also limits each execution to the following (which is similar to the Trial Tier limitations):

• Maximum of 4 Entities and 1GB per execution;

• No filters allowed;

• Only the DMM Professional version features are available.

IMPORTANT!

Take into account that license activations:

• Are final, 

• The number of DMM license activations is limited to the subscribed amount,

• Each licensed DMM in an OutSystems environment makes use of one license activation, and

• DMM activations cannot be un-activated and neither DMM licenses be re-used in another environment.

This means also you cannot uninstall DMM and reinstall in the same environment using the same license activation - you will use +1 activation in this process!

You can update the DMM application in an environment, the update of the DMM application by a new DMM version (from the FORGE or through an OAP) does not alter DMM's activation code use in that environment.

If you are using an OutSystems environment exclusively as a data origin of Data Migration through the REST API (for example, the production environment in the OutSystems PaaS Cloud), never using that environment as a destination or origin for other features like the Export, then that environment doesn't need an active DMM license.

To activate the license you just choose that option on the menu Management >> Online Activation:

This will pop-up  a form where you can enter your license ID and password, if we've already sent you one:

You can also ask us to activate you a license inside the DMM platform—assuming that your DMM installation has SMTP capabilities—by clicking on the "Request License Now" link near the top of the application.

You can also send an email to dmm.licensing@infosistema.com stating your name, email, and company name.

Either way that you decide to reach out to us, you will receive the instructions to activate the product and perform as many migrations as you need!

After you purchase your license, use the Activate License Now button (see images below), and a form where you can write the license information will appear. Then, the text on the top of the page will change to indicate the type of license you installed.

You will need to hit the Refresh button if you go over 30 days without using DMM, and are still within the license period - this way DMM will validate your license is still valid and allow you to use it:

Site Properties

There are a number of Site Properties that DMM has and you can change to get different behaviours. Don't change the properties marked as internal in the list below!