Deployment Guide
Information note
Note that some of the features detailed in this document may not apply and/or be available for the particular edition/version you are using.
This Talend Data Catalog (TDC)Deployment Guide includes the necessary documentation for the installation and configuration of the underlying software components:
- The Talend Data Catalog Application Server,
- based on the Meta Integration® Repository (MIR) for metadata storage (in a database server),
- and the Meta Integration® Model Bridge (MIMB) middleware for metadata harvesting.
This Talend Data Catalog (TDC) Deployment Guide includes only defines the minimal requirements to run the application server with reasonable performance based on the provided tutorial, or small business use cases. The actual requirements for enterprise-wide use cases based on larger models and configurations do require significantly greater resources to obtain acceptable performance.
The following requirements are based on:
- minimal to no network overhead (assuming both the database and Application servers to be locally installed on the same network),
- vendor's default install of the current version of their software (with all current service or fix packs),
- no other applications sharing such hardware (starting from a clean machine),
- Any other hardware/software configurations are acceptable as long as they provide the same (or better) results on the provided performance benchmark. In such case, if any problem is discovered (e.g. scalability or performance issues), then the customer must be able to reproduce the issue using an environment that conforms to the minimum performance requirements as defined herein.
- Potential known issues include (but are not limited to) the following:
- actual usable hardware performance on virtual environments (e.g VMWare configuration and licenses)
- network overhead on remote servers (e.g. bandwidth, proxy, VPN issues, VMWare inter OS network limitations without a proper license, etc.)
- shared resources with competing applications on the same OS, or between OS on a virtual environment,
- licensing limitations (e.g. most database server licenses limit the number of usable core/CPU)
- vendor software known limitations and requirements (e.g. Oracle on VMWare vs Oracle VM)