Talend Studio provides templates that allow you to create ready-to-run Jobs for common scenarios, such as Table to Table, File to Database, Table to File, etc. You can access these templates from the Repository > Job Designs > Create Job from Template menu. Joblet to File is not a valid template name.

To set up a server in your Talend environment that enables several members of your team to collaborate on a project, you need to enable two applications before working on a remote project: Git or SVN server instance and Talend Administration Center instance. These applications are used to manage version control and collaboration for your project.

Git or SVN server instance is a server application that allows you to store and track changes of your project files using a version control system. Git and SVN are two popular version control systems that are supported by Talend Studio. You need to have a Git or SVN server instance running and accessible by your team members before working on a remote project. You also need to have a Git or SVN client installed on each development workstation to connect to the server and perform version control operations.

Talend Administration Center is a web-based application that allows you to manage users, projects, tasks, execution servers, and licenses for your Talend environment. You need to have a Talend Administration Center instance running and accessible by your team members before working on a remote project. You also need to configure the team members and project settings in Talend Administration Center to grant access and permissions for your project.  References :  Talend Open Studio: Open-source ETL and Free Data Integration | Talend , [Version control - 7.3], [Talend Administration Center - 7.3]

The Use or register a shared DB Connection option in Talend Studio is an option that allows you to share a single database connection between multiple components in a job or between parent and child jobs. This option can improve the performance and efficiency of your job by avoiding opening and closing multiple connections to the same database. The Use or register a shared DB Connection option is compatible with the following scenarios:

Sharing a connection between parent and child jobs. You can use this option to pass a database connection from a parent job to a child job that is called by a tRunJob component. This way, you do not need to create a new connection in the child job, but reuse the existing one from the parent job.

Sharing a connection between components in the same subjob. You can use this option to register a database connection in one component (such as tMysqlConnection) and use it in other components (such as tMysqlInput or tMysqlOutput) in the same subjob. This way, you do not need to configure each component with the same connection properties, but use a shared one.

The Use or register a shared DB Connection option is incompatible with the following scenarios:

Using an independent process to run subjob option of tRunJob component. This option allows you to run a child job in a separate JVM process from the parent job. This option is not compatible with sharing a database connection, because each JVM process has its own memory space and cannot access the objects of another process.

Using dynamic job option of tRunJob component. This option allows you to call a child job dynamically based on a context variable that contains the name of the child job. This option is not compatible with sharing a database connection, because dynamic jobs are loaded at runtime and cannot access the metadata of other jobs.  References :  Talend Open Studio: Open-source ETL and Free Data Integration | Talend , [Use or register a shared DB Connection - 7.3], [tRunJob properties - 7.3]

The parameters that are defined in File Delimited metadata are:

Row separator: This parameter defines the character or string that separates each row of data in a delimited file. For example, a row separator can be a newline character (\n), a carriage return (\r), or a combination of both (\r\n).

File path: This parameter defines the location and name of the delimited file that you want to read or write. You can browse your local system or enter a URL to specify the file path. You can also use context variables or global variables to make the file path dynamic.

To retrieve records that have a specific value based on a variable, you can use a tDBInput component with a context variable in the SQL query. A context variable is a variable that can store a value that can be changed at runtime or between different contexts. A context variable can be used in various components to parameterize their properties or expressions. A tDBInput component is used to read data from a database table by executing an SQL query. You can use a context variable in the SQL query to filter the records based on a dynamic value. For example, if you have a context variable named country that stores the value of the country you want to filter by, you can use it in the SQL query of the tDBInput component as follows:

SELECT id, address, country FROM customers WHERE country = ‘context.country’

This will retrieve only the records that have the same value as the context variable country in the country column.

You do not need to use a Run if trigger, a tMatchGroup component, or a tFilterColumns component to achieve this. A Run if trigger is used to execute a subjob conditionally based on a logical expression. A tMatchGroup component is used to group similar records based on matching rules and output them as master or duplicate records. A tFilterColumns component is used to select or remove columns from an input flow based on a list of column names.  References :  Talend Open Studio: Open-source ETL and Free Data Integration | Talend , [Contexts - 7.3], [tDBInput properties - 7.3] , [Run if properties - 7.3], [tMatchGroup properties - 7.3] , [tFilterColumns properties - 7.3]

The tMap component allows you to set up a filter on the input fields by using the Expression filter in the output table. The Expression filter is a field where you can enter a logical expression that evaluates to true or false for each input row. For example, if you want to filter out the rows that have null values in a certain column, you can use row1.column != null as the expression filter for that output. The expression filter applies to all the input fields of the row, not just a single column. You cannot set up a filter on the input fields by using the Match Model parameter field for one of the inputs or outputs, as this field is used to define how to match rows between different inputs or outputs based on a key attribute.  References :  Talend Open Studio: Open-source ETL and Free Data Integration | Talend