1.Basic system requirements like memory for client and server systems.
-Client = graphical designer studio : 1Go Memory is appreciate (512Mo minimum)
-Server = administrator console and jobserver : 4Go and more appreciate (2Go minimum, it depends of Data Integration processus)
2.On which platforms the client and server can be run?
-Client = graphical designer studio (Windows, Linux, MAC OS), all Operating system supporting JVM 1.5 and higher + a window manager
-Server = administrator console and jobserver : all platforms supporting JVM 1.5 and higher (Windows, Linux, MAC OS, UNIX, AIX, HP UX, AS400, MVS, ...)
3.How is the exception handling reported(ex: through flat files etc).
Flat files or databases (every databases) or both.
Activity Monitoring Console display and present exception handling, statistics, status, data volume in a graphical and charts representation.
4.Basic architecture of Talend whether it is a Client-Server Architecture.
Not exactly. We are a code generator engine. The Job that you design into the Studio generates JAVA or PERL or SQL standard and autonomous process.
5.Version Control Capability.
Version control available.
Talend Open Studio : Local Repository stored in file system (single user).
Talend Integration Suite : Remote and shared Repository stored in subversion (team work).
6.Support for designing Datamarts.
8.Any Options provided for Performance Tuning.
Yes = ELT, Parallelize, BulkLoad, and so on
9.Security like Encription Provided.
10.Impact Anaalysis Capability.
Yes, but Data Lineage not yes available.
The first response by Talend team says the minimum memory required is 512Mo but 1Go is appreciated. But then latest response says you need minimum 2Go. Which is true of these?
And regarding JVM. Wich edition (jobserver, admin, TIS Studio, MDM, TOS...) needs JRE and wich one needs JDK?
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema
Pick up some tips and tricks with Context Variables