Data Flow - From Petals to a Job using a tPetalsInput

Preliminary notes

This use case can only be reproduced with Talend Integration Suite.
People using Talend Open Studio can find an alternative in the use case "Data Flow - From Petals to a job using attachments".

Rationale

Send a data flow from Petals into a Talend job, that will insert these data into a database.

The input message provides the data flow.
Only the job's result is expected in the response.

Creating and exporting the job

The job to be executed performs the following actions:

  1. The job is passed the data flow coming from Petals.
  2. The job connects to a database and writes the data flow in this database.

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).

Creating the job

The job creation is detailled in the use case "A Simple Talend Job".
There is no difference.

Exporting the job

Deploying and testing in Petals

Looking at the created archive

The created archive is a Petals service assembly.
More details are available in the documentation of the petals-SE-Talend.

What must be taken care of is the jbi.xml and the WSDL files available in the service-unit.
If you open the created archive, it contains another archive. This second archive contains a jbi.xml file.

The WSDL file exposes no parameter.
The possible input parameters are:

Deploying and testing this new service

SoapUI is used for this test...

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.