{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 case "Data Flow - From Petals to a job using a tPetalsInput".

h1. Rationale

Send a CSV file as an attachment through Petals to a Talend job.
The job loads the content of the attached file and inserts its content into a database.
In the scope of this use case, we could imagine, even if it is not shown, that the file's content is transformed before being inserted.


The input message provides the attachment file.
Only the job's result is expected in the response.

h1. Creating and exporting the job

The job to be executed performs the following actions:
# The job is passed the file whose content must be inserted. The file is passed as an attachment to the message.
# The job loads the file's content.
# The job connects to a database and writes the data in this database.

This job has one context variable, pointing to the location of the file whose content must be loaded.


h2. Creating the job

The job is made up of two components:
# The tFileInputDelimited reads the CSV file's content.
# The tMySqlOutput writes the data into the database.

Here is the overall aspect of the job.

!PetalsToJob_file_job.jpg!

\\
Here is the schema of the tFileInputDelimited component.

!PetalsToJob_file_tfidschema.jpg!

\\
Here are the properties of the tFileInputDelimited component.

!PetalsToJob_file_tfidsproperties.jpg!

\\
Here are the properties of the tMySqlOutput component.

!PetalsToJob_file_tmoproperties.jpg!


h2. Exporting the job

Select the job and right-click it. Select *Export Job Scripts*.
In the *Export type* combo, select *Petals ESB*.
Update the target destination and let the job be exposed as a singleton.

Click *Edit the exposed contexts*.
A dialog shows up. Click the *Export mode* column, and select *Parameter* in the combo box. Click *OK*.

You should have the following dialog:

!InAtt.jpg!

The link label should be updated and indicate the number of exported contexts.
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 only expects the input attachment.

{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:element name="outputLocation" nillable="true" type="tns:attachment" />
</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.

{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

Since we use attachments, we will prefer using a Java client instead of SoapUI.
However, it is possible to use SoapUI to send or receive messages with attachments. Just make sure the MTOM property is activated.

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

\\
Then, to generate a client from the WSDL, you can use Apache CXF or Axis2.
As an example, the following code was generated with Apache CXF 2.2.6.
Check the CXF documentation to see how to develop a service consumer in Java.

\\
Only the main client class is shown here.
The client's code is the following:

{code:lang=java}
package org.ow2.petals.talend;

/**
* Please modify this class to meet your needs This class is not complete
*/

import java.io.File;
import java.net.MalformedURLException;
import java.net.URL;

import javax.activation.DataHandler;
import javax.activation.FileDataSource;
import javax.xml.namespace.QName;
import javax.xml.ws.BindingProvider;
import javax.xml.ws.soap.SOAPBinding;

import net.java.dev.jaxb.array.StringArray;

/**
* This class was generated by Apache CXF 2.2.6 Mon Mar 29 18:38:51 CEST 2010

/**

/**
* Main method.
* @param args
* @throws Exception
*/

try {
if( wsdlFile.exists()) {
wsdlURL = wsdlFile.toURI().toURL();
}
else {
wsdlURL = new URL( args[ 0 ]);
}
} catch( MalformedURLException e ) {
e.printStackTrace();
}

((SOAPBinding) ((BindingProvider) port).getBinding()).setMTOMEnabled( true );
//

// Set the input attachment
File f = new File( "C:/Documents and Settings/vzurczak/Bureau/in.csv" );
DataHandler dh = new DataHandler( new FileDataSource( f ));
Attachment att = new Attachment();
att.setFileContent( dh );

InAttachments ia = new InAttachments();
// Notice: outputLocation is the name of the context in the job.
// The Talend export propagated the name in the service's WSDL.
ia.setOutputLocation( att );
//

{
System.out.println( "Invoking executeJob..." );
org.ow2.petals.talend.TalendContexts contexts = null;
java.util.List<org.ow2.petals.talend.InRow> inDataBean = null;
java.util.List<java.lang.String> talendOption = null;
try {
org.ow2.petals.talend.TalendJobOutput result = port
.executeJob( contexts,
ia,
inDataBean,
talendOption );

if( result == null )
System.out.println( "Something went wrong, the result is null." );
else {
// The job's result
System.out.println( "Job's result = " );

int cpt = 0;
for( StringArray row : result.getExecutionResult()) {
System.out.print( "Row " + cpt++ + ": " );
for( String col : row.getItem())
System.out.print( col + " ; " );
}
}

} catch( TalendTechnicalException_Exception e ) {
System.out.println( "Expected exception: TalendTechnicalException has occurred." );
System.out.println( e.toString());

} catch( TalendBusinessException_Exception e ) {
System.out.println( "Expected exception: TalendBusinessException has occurred." );
System.out.println( e.toString());
}
}

System.exit( 0 );
}
}
{code}

\\
Notice that the MTOM-mode was activated. Not enabling it will result in errors.

\\
The execution output (displayed in the console) is:

{noformat}
Invoking executeJob...
Job's result =
Row 0: 0 ;
{noformat}

If the job execution fails, the 0 is replaced by another integer, e.g. 1.
One failure reason can be, as an example, that the database is not started.

To determine the act cause of a problem, you would have to use logging features available in the Talend palet.
However, let's make it clear, the job's logs are managed independently of Petals and its monitoring capabilities.
{column}
{column:width=350px}
{panel:title=Table of contents}{toc}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}