Skip to main content Skip to complementary content

Creating a connection to the MDM server

Each MDM project requires a connection to at least one MDM server.

If you installed the Talend product via the Talend Installer, the MDM Server should automatically start at system boot. If it's not running for any reason, go to the mdm folder under the Talend product directory and run the start_mdm batch command.

Before you begin

Make sure that the MDM server is up and running before launching Talend Studio.

Procedure

  1. In the Talend Studio main window, in the Server Explorer panel, click the [+] button to specify a new MDM server location.
    The Add Server Location dialog box pops up.

    You can have more than one active connection to the MDM server using different authentication information.

  2. In the Name field, enter a name or description for the MDM server to which you want to connect.
    You can then choose this alias to refer to the server from different points in Talend Studio. This simplifies deployment of MDM related integration and quality Jobs.
  3. In the Server field, enter the URL of the MDM server to which you want to connect.
    The server URL is structured as follows:
    http://[server address or server name]:[server port]/talendmdm/services/soap
    .
  4. Enter admin as the user name and talend as the password.
    When you connect to Talend Studio as a Talend administrator, you have the rights only to manage roles and access control in Talend Studio, but you do not have any of the rights of the System-Admin. For further information on user roles and access rights, see Talend Studio User Guide.
  5. Select the Share Password check box if you want to save your login credentials and avoid having to enter your password on every connection.
    This option only applies to Git projects. For local projects, it is grayed out.
  6. Click OK to close the dialog box.

Results

A connection to the MDM server is created.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!