{section}
{column}

h1. Preliminary notes

This use case can be reproduced with both Talend Open Studio and Talend Integration Suite.
It is an alternative way to undertake what is done in the use cases "Data Flow - From a job to Petals using a tPetalsOutput" and "Data Flow - From a job to Petals using attachments".
{column}
{column:width=360px}
{panel}{toc}{panel}
{column}{section}

h1. Rationale

Generate a data flow in a job and send it inside Petals.

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

h1. Creating and exporting the job

The job to be executed performs the following actions:
# The job generates a data flow.
# This data flow is sent into Petals.

This job has no context variable.


h2. Creating the job

The job is made up of two components:
# The tRowGenerator generates the data flow.
# The tBufferOutput puts this data in the job's result, thus making it available in Petals.

Here is the overall aspect of the job.

!JobToPetals_buf_job.jpg!\\

\\
Here is the schema and the generation settings for the tRowGenerator component.

!JobToPetals_buf_trgschema.jpg!

\\
Here is the schema of the tBufferOutput component.

!JobToPetals_buf_tboschema.jpg!



h2. Exporting the job

Select the job and right-click it. Select *Export to Petals ESB*.
Update the target destination.
Let the job be exposed as a singleton.


You should have the following dialog:

!JobToPetals_buf_export.jpg!

Click *Finish*.



h1. Deploying and testing in Petals


h2. Looking at the generated WSDL

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.

\\
The input message's description expects no parameter.

{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:sequence>
</xs:complexType>

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

<xs:complexType name="inRow">
<xs:sequence>
</xs:sequence>
</xs:complexType>
{code}

\\
And the output message only includes the job's result.
It is the job's result which will contain the generated data flow.

{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

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 (in SoapUI) should look like this:

<soapenv:Header/>
<soapenv:Body>
<tal:executeJob>
<!--Optional:-->
<tal:contexts/>
<!--Optional:-->
<tal:in-attachments/>
<!--Zero or more repetitions:-->
<tal:in-data-bean/>
</tal:executeJob>
</soapenv:Body>
</soapenv:Envelope>
{code}

<tns:talend-job-output>
<tns:executionResult>
<jaxb:item>pj6ySPq9ZsyyDCf</jaxb:item>
<jaxb:item>88</jaxb:item>
</tns:executionResult>
<tns:executionResult>
<jaxb:item>nUfyq4kbUJ8vBgw</jaxb:item>
<jaxb:item>12</jaxb:item>
</tns:executionResult>

<!-- ... -->

<tns:executionResult>
<jaxb:item>hoVgFrBo3leVdaG</jaxb:item>
<jaxb:item>97</jaxb:item>
</tns:executionResult>
<tns:outAttachment/>
</tns:talend-job-output>
</tns:executeJobResponse>
</soapenv:Body>
</soapenv:Envelope>
{code}

\\
If the job execution fails, then it should just return an integer, e.g. 1.