Hi again Petals Padawan. Glad to see you're still on board \!
For your 3rd day, you will connect Petals to an FTP server, and expose the created FTP service as a SOAP web-service, outside Petals ESB.
{panel:title=Last tested with}
* Petals ESB 3.1
* Petals Studio 1.1.0
* Petals SE RMI 1.1.1
* Petals BC SOAP 4.0.2
* Petals Webconsole 2.0.4
* Tomcat 6.0.29
* JDK 6 update 20

*Added in this tutorial :*
* Petals BC FTP 3.2.1
* soapUI 3.6
{panel}

# File => New => Service Unit Project: Service Unit - Select the kind of service to create.
# Select: Provide / FTP / Current_Version => Next: FTP Service-Unit - Defines the JBI properties of the service to import.
## Service Name: *FtpTutorial*
# Next => Next: FTP Service-Unit - Define the specific properties for this version of the component.
{note}<folder> attribute is written as optionnal in Studio, but it is not. It will be optional in BC-FTP v3, so as soon as it is published, you will not need to specify the folder attribute for the tutorial.{note}
## Server: *ftp.petalslink.com*
## Port: *21*
## User: *petals*
## Password: *demo*
## Folder: *_/_*
## Transfer Type: *auto*
## Connection Mode: *active*
# Finish.
# Look the generated _jbi.xml_ component configuration. It should look like:
{code:lang=xml|title=jbi.xml}<jbi:provides
interface-name="generatedNs:FtpInterface"
service-name="generatedNs:FtpTutorial"
endpoint-name="FtpTutorialEndpoint">

<\!-\- CDK specific elements -->
<petalsCDK:timeout>30000</petalsCDK:timeout>
<petalsCDK:validate-wsdl>true</petalsCDK:validate-wsdl>
<petalsCDK:forward-security-subject>false</petalsCDK:forward-security-subject>
<petalsCDK:forward-message-properties>false</petalsCDK:forward-message-properties>
<petalsCDK:forward-attachments>false</petalsCDK:forward-attachments>
<petalsCDK:wsdl>FtpService.wsdl</petalsCDK:wsdl>

<\!-\- Component specific elements -->
<ftp:server>ftp.petalslink.com</ftp:server>
<ftp:port>21</ftp:port>
<ftp:user>petals</ftp:user>
<ftp:password>demo</ftp:password>
<ftp:folder>/</ftp:folder>
<ftp:transfer-type>auto</ftp:transfer-type>
<ftp:connection-mode>active</ftp:connection-mode>
</jbi:provides>{code}

# Look the generated _FtpService.wsdl_ sources. Operations available on service are described here.
# On the left "Petals projects" tree, right click on the Service-Unit Project "_su-FtpTutorial-provide_" => Petals => Fast Export for Petals.
{note:title=Known bug for Studio v1.1.0 !}Please check jbi.xml and FtpService \!
"interface-name" attribute in _jbi.xml_ and "portType name" in the WSDL should have the same value. If not, please correct _FtpService.wsdl_ :
# SELECT:
<wsdl:portType name="Ftp">
# REPLACE BY:

# Select:
## Endpoint: FtpTutorialEndpoint
## Operation: dir
## MEP: InOut
# Submit

Before, we used SOAP to import WSDL to create services inside Petals ESB. Meaning _Provide_ a SOAP service inside the bus.

<soapenv:Header/>
<soapenv:Body>
<ver:dir>
</ver:dir>
</soapenv:Body>
</soapenv:Envelope>
{code}
# Clic the green arrow to send the message. The response should list two files.
{info:title=Want to go further?}Try reading "HelloWorld.txt" into "Integration" folder, with optional elements.
\\
You can keep the optional elements, to change the initial BC-FTP configuration. But you need to redefine ALL properties in this case.

*DONE. Bravo \!*
Now you know how to:

* Connect Petals ESB to an FTP Server and call operations.
* Monitor service exchanges in Webconsole.
* Expose a Petals Service as external SOAP Web-service.
* Test a web-service with soapUI.

This was more "real" usecase, hum ? Difficulty goes increasing, your knowledge as well.

*Tomorrow you will create a Petals service based on a custom Java class (annotated JSR 181)*