The operating principles could be summarized into the following major topics:
- building technical or business-related processes,
- administrating users, projects, access rights, and processes and their dependencies,
- deploying and executing technical processes,
- monitoring the execution of the technical processes.
Each of the above topics has been graphically described by isolating specific functionalities in different functional blocks.
The availability of some functionalities depends on your license. For more information on which functionalities are available to you, see What modules and features are available depending on your license.
The chart shows the functional blocks involved in building technical processes, managing projects and administrating users' accounts:
In this description, several color-based types of functional blocks are defined:
- The CLIENTS block includes one or more Studio APIs and Web
browsers that could be on the same or on different machines.
From the Studio API, end-users can carry out technical processes: data integration processes (named Jobs), data service processes (named Services), or mediation Routes. From the Studio, Jobs, Services and Routes can be published on the Nexus Artifact Repository. The Studio allows the user to work on any project for which he has authorization for.
From the Web browser, end-users connect to the remotely based Administration Center through a secured HTTP protocol.
The end-user category in this description may include developers, project managers, administrators and any other person involved in building technical processes. Each of these end-users will use either the Studio or the Administration Center or both of them depending on the enterprise policy. For more information about users' rights and roles, see User roles/rights in the Administration Center.
- The TALEND SERVERS and DATABASES blocks and the Git grey circle include a web-based
Administration Center (application server) connected to two shared repositories:
one based on an Git server and one based on a database server (Admin).
The Administration Center enables the management and administration of all projects. Administration metadata (user accounts, access rights and project authorization for example) is stored in the database server and project metadata (Jobs, Routines, Routes, Services, for example) is stored in the Git server to easily share them between the different end-users.
Deployment and execution
The chart also shows the execution servers (JobServers and Talend Runtimes) and the Nexus Artifact Repository. Artifact Repository is involved in publishing Jobs, Web, REST and data services, and mediation routes created in the studio or any other Java IDE, and the execution server is involved in deploying and executing them:
- The Nexus grey circle represents the Artifact Repository that stores all Jobs, Routes and Services that are published from the Studio and are ready to be deployed and executed in the execution server.
- The TALEND EXECUTION SERVERS block represents the execution
servers that run the technical processes according to the execution scheduling
set up in the Talend Administration Center Web
application. Those execution servers can be:
- One or more Talend Runtimes
(execution container) deployed inside your information system. The
deploys and executes the Jobs, Routes and Services retrieved from the
Artifact Repository according to the set up defined in the
Administration Center via the web application.
If you have several Talend Runtimes on which to deploy the artifacts, you will be able to load balance their execution according to your needs. All instances of Talend Runtime will communicate between each other via the Service Locator to identify the one more likely to deploy and execute the artifact(s) set to deployment in Talend Administration Center. The Talend Runtime elected for the deployment will request for the artifact(s) to deploy and execute from the Artifact Repository and the Artifact Repository will thus send the artifact(s) requested along with all the dependencies needed for its/their execution to the Talend Runtime, that will deploy and execute them.
- One or more JobServers deployed inside your information system that run technical processes (Jobs) according to scheduled time, date or event set in the Talend Administration Center Web application.
- One or more Talend Runtimes (execution container) deployed inside your information system. The Talend Runtime deploys and executes the Jobs, Routes and Services retrieved from the Artifact Repository according to the set up defined in the Administration Center via the web application.
For more information on how to manage deployment, see Executing Jobs, Routes and Services.
The chart also shows the Monitoring module:
The Monitoring green circle shows the Service Activity Monitoring.
The Service Activity Monitoring allows the end-users to monitor service calls. It provides monitoring and consolidated event information that the end-user can use to understand the underlying requests and replies that compose the event, monitor faults that may be unexpectedly generated and support the system management decisions. For more information, see Monitoring the Service activity.