Petals Documentation > Petals ESB > Petals Components > Page Comparison - Data Flow - From a Job to Petals using Attachments (v.5 vs v.6)

Data Flow - From a Job to Petals using Attachments

Version 5 by Charles Casadei
on Mar 16, 2010 10:08.
<< Changes from 4 to 5
compared with
Version 6 by Vincent Zurczak
on Mar 31, 2010 22:01.
Changes from 6 to 7 >>
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (19)

View Page History
{section}
{column}

h1. Preliminary notes

...
In the export mode, select *OUT-Attachment* or *Parameter and OUT-Attachment*.

In the scope of this use case, we are going to use *OUT-Attachment*.
Consequently, the file location is the default one, defined in the job (cannot be null).

You should have the following dialog:
...
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.
Just make sure the SOAP configuration uses the *InOut* MEP and calls the *executeJob* method.

\\
Then, to generate a client from the WSDL, you can use Apache CXF or Axis2.
In the scope of this use case, Apache CXF is used. Only the client class is shown here.
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;
TODO
/**
* Please modify this class to meet your needs This class is not complete
*/

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

import javax.xml.namespace.QName;
import javax.xml.ws.BindingProvider;
import javax.xml.ws.soap.SOAPBinding;

/**
* This class was generated by Apache CXF 2.2.6 Wed Mar 31 21:57:39 CEST 2010
* Generated source version: 2.2.6
*/
public final class Client {

private static final QName SERVICE_NAME = new QName(
"http://petals.ow2.org/talend/", "GeneratedXmlService" );


/**
* Constructor.
*/
private Client() {
// nothing
}


/**
* Main method.
* @param args
* @throws Exception
*/
public static void main( String args[] ) throws Exception {

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

GeneratedXmlService ss = new GeneratedXmlService( wsdlURL, SERVICE_NAME );
GeneratedXmlServicePortType port = ss.getGeneratedXmlEndpoint();

// Activate the MTOM mode
((SOAPBinding) ((BindingProvider) port).getBinding()).setMTOMEnabled( true );
//

System.out.println( "Invoking executeJob..." );
org.ow2.petals.talend.TalendContexts contexts = null;
org.ow2.petals.talend.InAttachments inAttachments = 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,
inAttachments,
inDataBean,
talendOption );

// Get the output attachment
if( result == null )
System.out.println( "Something went wrong. The result is null." );
else {
boolean errorOccured = true;
if( result.getOutAttachment() != null ) {

// Notice that "outputLocation" is the name of the context variable we exported.
// The Talend export propagated its name in the WSDL.
Attachment att = result.getOutAttachment().getOutputLocation();
if( att != null ) {
InputStream is = null;
FileOutputStream fos = null;

try {
is = att.getFileContent().getInputStream();;
fos = new FileOutputStream( new File(
"C:/Documents and Settings/vzurczak/Bureau/outputXml.xml" ));

byte[] buf = new byte[ 1024 ];
int len;
while((len = is.read( buf )) > 0) {
fos.write( buf, 0, len );
}

errorOccured = false;

} finally {
if( is != null )
is.close();
if( fos != null )
fos.close();
}
}
}

// Check what happened
if( errorOccured )
System.out.println( "Something went wrong. Good luck for debugging!" );
else
System.out.println( "OK." );
}

} 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...
todo OK.
{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}
...