Talend Metadata Manager architecture - 6.5

Talend Metadata Manager: Explorer User Guide

Talend Metadata Manager
Talend Metadata Manager Platform
Talend Metadata Manager Platform Advanced
Design and Development
Talend Metadata Manager consists of two modules, that are installed as services: Talend Metadata Manager application server and Talend Metadata Manager database.

Talend Metadata Manager application server architecture

Talend Metadata Manager is a three-tier application.

  • The Client tier, with a Web browser and a scripting client.

    From the Web browser, you administer and use the Talend Metadata Manager features. The user interface is a rich web application that works across all major Web browsers, built using a client-side web application JavaScript framework.

    The scripting client allows you to automate administration tasks, such as create a folder and harvest a model upon changes, and execute model management operations, such as compare, migrate or stitch models. All basic capabilities available to the user interface are scriptable.

  • The Server tier is a web J2EE application (WAR) that can run in a web container/application server. It uses a tomcat server by default and runs as a standard web application named MM. By default, this server is accessible on port 11480.

  • The Database tier is a database used to store data and run computations on. As a rule, Talend Metadata Manager uses the database to perform computations on data that can potentially exceed the amount of available server memory.

    By default, this is a PostgreSQL database server where all repository information will be stored. Oracle and MS SQLServer are also supported.

    When multiple users access Talend Metadata Manager simultaneously, the database can become the key feature for client performance. In this case, you should consider scaling up the database performance by adding more computational resources (such as CPUs) or speeding up the database storage (such as RAID, faster disks, etc.).

Talend Metadata Manager deployment architecture

The standard deployment architecture includes the following modules:
  • Talend Metadata Manager application server
  • Database server

    The database server should be in "close proximity" to the application server in terms of network connectivity, as there is a high degree of traffic between these two.

  • One or more Metadata Harvesting agents

    A metadata harvesting agent is a metadata harvesting server, installed on a machine remote to the application server. These are often necessary when it is not possible to install APIs, which are required for harvesting bridge function, on the application server itself.

    In this case, a metadata harvesting agent is installed on this machine as well as the API for the metadata source technology (generally a client installation). Then, Talend Metadata Manager uses this machine as an agent to harvest from or export to that source technology.

  • Workstations

    All administrative and analysis activities are generally conducted from personal workstations with a supported Web browser.