If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

MDM Ataccama Cloud Deployment

This article is applicable to Ataccama Cloud deployments only.

MDM can be deployed as an Ataccama Cloud application.

Currently, this option cannot be used for production environments.

Configuration summary

The following steps must be completed to run MDM in Ataccama Cloud:

Ataccama provides the credentials of your environment and a Git server used to store MDM server configurations.
Download and configure a corresponding version of ONE Desktop.
Push an MDM server configuration to the provided Git server.
Deploy a valid configuration from the MDM Web App Admin Center.

We recommend you test MDM server configurations locally. For more information, see MDM Project Local Server Configuration Testing.

Download ONE Desktop

You can download the needed version of ONE Desktop from the Downloads page.

Create and configure a new project

Launch ONE Desktop.
Switch to the Model Explorer view and select the New Model Project icon. Give the project a name, in Use template select General MDM project - blank, and then select Finish to confirm.

A new MDM project is created:
Configure your MDM project. For instructions, see the articles in the MDM Project Configuration section in MDM documentation.

Connect Git with ONE Desktop and your cloud environment

MDM server configurations must be stored in a Git server. The connection to this server must first be configured in ONE Desktop and the Ataccama Cloud configuration interface (Cloud Portal).

For information about how to work with Git in ONE Desktop, see Git.

The root of your Git repository must contain the following folders:

mdm
- runtime
- Files

To ensure the correct structure and that all necessary files are present, you can copy the folders and their content from the MDM project created in the Create and configure a new project step.

Your Ataccama Cloud deployment should also contain a pathvariables.xml file in the runtime folder.

There are additional files that enable you to deploy alternative server configurations. However, these are not necessary to run the default configuration.

For more information, see MDM Project Local Server Configuration Testing.

We recommend creating different branches for development, testing, and production purposes and connecting them to equivalent Ataccama Cloud environments.

Your Git project should have the following branches:

Dev branch.
Test branch.
Prod branch.

To help distinguish which branch is being used and the purpose of the environment, we recommend you also add dev, test, and prod to the name of the relevant environments in Cloud Portal.

To connect your cloud environment to the Git server:

Go to Ataccama Cloud Portal, that is, your configuration interface.
Select an environment from the list of environments.
Go to the Services tab.
In the Master Data Management section, find the MDM Server and select Settings.
In Edit connection, complete the information as follows:
1. Connection: Choose between HTTPS and SSH connection type.
2. Git server: Provide the Git server URL.
3. Initial branch: Specify the initial branch to be used.
4. Provide authentication credentials depending on the chosen connection type.
  - For HTTPS connection provide the following:
    
    Git username.
    
    Git password.
  - For SSH connection upload a Private SSH key.

The validity of the Git server configuration can later be verified in the MDM Web App Admin Center.

You can now make changes to the configuration and push these changes to your cloud environment. You can manage these configurations from the MDM Web App Admin Center. For more information, see MDM Web App Admin Center.

Deploy web application configuration

After setting up everything needed for you MDM solution, you need to generate XML configuration files (packed into a ZIP archive) and deploy them to the MDM Web App.

You need to perform this step every time you make changes to your project.

Was this page useful?