Petals Documentation > Petals ESB > Petals Components > Page Comparison - A Simple Talend Job - Getting the Result File as an Attachment (v.2 vs v.3)

A Simple Talend Job - Getting the Result File as an Attachment

Version 2 by Vincent Zurczak
on Mar 04, 2010 12:18.
<< Changes from 1 to 2
compared with
Version 3 by Vincent Zurczak
on Mar 05, 2010 15:15.
Changes from 3 to 4 >>
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (22)

View Page History
{section}
{column}

h1. Preliminary notes

This use case can only be reproduced with Talend Integration Suite.
This use case relies on the use case "A Simple Talend Job".
{column}
{column:width=360px}
{panel}{toc}{panel}
{column}{section}

h1. Rationale
...



The input message provides no information.
The response is made up of two parts:
* The job's result (String\[\]\[\]).
* The job's result (an array of array of String).
* The created file, as an output attachment.

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

\\
{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}

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


h2. Creating the job

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


h2. Exporting the job

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



h1. Deploying and testing in Petals


h2. Looking at the created archive generated WSDL

The created archive is a Petals service assembly.
More details are available in the documentation of the petals-SE-Talend.
In the created Petals service assembly, the most interesting thing to look at is the WSDL.
Indeed, the WSDL will determine the way the exported service will be called.

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 input message's description requires empty parameters.

The WSDL file exposes no parameter.
The possible input parameters are:
{code:lang=xml}
<xs:element name="executeJob" type="tns:executeJob" />
<xs:complexType name="executeJob">
<xs:sequence>
<xs:element minOccurs="0" name="contexts" type="tns:talendContexts" />
<xs:element minOccurs="0" name="in-attachments" type="tns:inAttachments" />
<xs:element maxOccurs="unbounded" minOccurs="0" name="in-data-bean" type="tns:inRow" />
<xs:element maxOccurs="unbounded" minOccurs="0" name="talend-option" type="xs:string" />
</xs:sequence>
</xs:complexType>

<xs:complexType name="talendContexts">
<xs:sequence>
<xs:element name="outputLocation" type="xs:string" minOccurs="0"
default="C:/Documents and Settings/vzurczak/Bureau/output.csv" />
</xs:sequence>
</xs:complexType>

<xs:complexType name="inAttachments">
<xs:sequence>
</xs:sequence>
</xs:complexType>

<xs:complexType name="inRow">
<xs:sequence>
</xs:sequence>
</xs:complexType>

{code}

\\
As you can see, the context name, type and default value have been exported in the generated WSDL.
In any case, the default value is more useful to document the service than for the execution.

{note}
Obviously, the file path example to illustrate a context may not be the best one.
Anyway, it serves its purpose, which is being an example.
{note}

\\
And the output message only includes the job's result.

{code:lang=xml}
<xs:element name="executeJobResponse" type="tns:executeJobResponse" />
<xs:complexType name="executeJobResponse">
<xs:sequence>
<xs:element minOccurs="0" name="talend-job-output" type="tns:talendJobOutput" />
</xs:sequence>
</xs:complexType>

<xs:complexType name="talendJobOutput">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="executionResult" nillable="true" type="ns1:stringArray" />
<xs:element minOccurs="0" name="outAttachment" type="tns:outAttachments" />
<xs:element maxOccurs="unbounded" minOccurs="0" name="outDataBean" nillable="true" type="tns:outRow" />
</xs:sequence>
</xs:complexType>

<xs:complexType name="outAttachments">
<xs:sequence>
</xs:sequence>
</xs:complexType>

<xs:complexType name="outRow">
<xs:sequence>
</xs:sequence>
</xs:complexType>

{code}


h2. Deploying and testing this new service

SoapUI is used for this test...
To test this service, you can use a tool like SoapUI.
This way, you can see what the XML messages look like.

The first thing to do is to create a service-unit for the Petals-BC-SOAP component, that exposes (consumes) our _Talend job as a service_ outside the bus.
This step is not described here. You can take a look at the Petals-BC-SOAP documentation and the Petals Studio documentation.
Just make sure the SOAP configuration uses the InOut MEP.

\\
Now, your input message should be:

{code:lang=xml}

{code}

\\
And the returned message should be:

{code:lang=xml}

{code}