E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (13)
View Page History
...
h1. Preliminary notes h1. Rationale
Execute a Talend job into Petals and passing it a context as a parameter described in the service's WSDL interface.
The resulting file will be returned as an attachement
The resulting file will be returned as an attachement
Send a data flow from Petals into a Talend job, that will insert these data into a database.
The job is exposed as a service into Petals. When this service is called, the parameter is passed to the job, which is then executed.
The file created by this job is then returned as an attchment.
The file created by this job is then returned as an attchment.
The input message provides the value of of the context which is exposed as a parameter in the service's interface.
The input message provides the data flow.
Only the job's result is expected in the response.
...The job to be executed performs the following actions:
# The job is passed the value of the context variable. data flow coming from Petals.
# The job connects to a database and writes the data flow in this database.
# It retrieves the content of a table.
# It serializes part of the extracted data as a CSV file on the disk.
# Once the execution terminated, the created file is attached to the returned message.
# It serializes part of the extracted data as a CSV file on the disk.
# Once the execution terminated, the created file is attached to the returned message.
This job has one context variable, which indicates the location of the CSV file.
This location will be read by the Petals-SE-Talend component once the execution is terminated. The file will then be attached to the returned message.
This location will be read by the Petals-SE-Talend component once the execution is terminated. The file will then be attached to the returned message.
This job has no context variable.
In the scope of this use case, it is assumed there is a database "formationtalend" on the localhost, having a table named customers.
The schema of the customers table includes two columns named "CustomerName" and CustomerAddress, both being of type varchar(255).
The schema of the customers table includes two columns named "CustomerName" and CustomerAddress, both being of type varchar(255).
{info}
In the scope of this use case, it is assumed there is a database formationtalend on the localhost, having a table named customers.
The schema of the customers table includes two columns named CustomerName and CustomerAddress, both being of type varchar(255).
{info}
The schema of the customers table includes two columns named CustomerName and CustomerAddress, both being of type varchar(255).
{info}
h2. Creating the job
...