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}
h2. Deploy a FTP Service Unit
*Install and Deploy BC-FTP*
* [Download Petals-BC-FTP|http://petals.ow2.org/download-jbi-components.html].
* Deploy BC-FTP in Petals ESB.
*Configure and deploy a FTP Service-Unit for* *[ftp.petalslink.com]*
# Start Petals ESB.
# Launch Petals Studio.
# 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.
## Server: *ftp.petalslink.com*
## Port: *21*
## User: *petals*
## Password: *demo*
## Folder: *_/_*
## Transfer Type: *auto*
## Connection Mode: *active*
{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}
# 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:
<wsdl:portType name="FtpInterface">
This is a known bug in Petals Studio 1.1.0. It should be corrected in version 1.1.1{note}
# Drop the generated _sa-FTP-FtpTutorial-provide.zip_ to ./_petals-platform-xxx/install/_ folder to deploy it.
# Check Petals ESB traces to be sure the SA was deployed successfully.
h2. Test and monitor in Webconsole
*Send test DIR Operation on root folder*
# Start the Webconsole
# Server:0 => Text panel => Send
# Select:
## Endpoint: FtpTutorialEndpoint
## Operation: dir
## MEP: InOut
# Submit
The response message should list files on the Ftp.
*Monitor services*
# In Webconsole, go to tab: Monitoring / Server Monitoring
# Check "Filter endpoint"
# Select Endpoint: FtpTutorialEndpoint
{info} You can also create filters based on Interface name, Service Name or Operation Name. This is useful for example if one service is duplicated on multiple endpoints.{info}
# Submit. FtpTutorial is now listed in exchange filters
# Activate monitoring on FtpTutorialEndpointby clicking the small icon in the "Monitoring column" to .
# Send a few test messages from the test panel
# Go in tab: Monitoring/Filter Monitoring
*Change destination folder*
# Got to [ftp://ftp.petalslink.com] in your web or ftp browser, using previous login. You see there is an "Integration" folder. Let's go there.
# Go to Petals Studio
# Edit FtpTutorial _jbi.xml_
# Change <folder>/</folder> to <folder>Integration</folder>
*Redeploy the component*
# Go in Webconsole/Server:0/Administration/Service-Assemblies
# Uninstall the previous FtpTutorial SA (Stop=>Shutdown=>Uninstall)
{info}As for installing, you can use three methods:
* Webconsole. Stop=>Shutdown=>Uninstall (alternatives if needed: "force undeploy" or "clear all")
* Autoloader: Remove the corresponding .ZIP package from _./petals-platform-xxx/installed/_
* Command Line: _hu_ or _hotundeploy_. Ex: _"hu sa-FTP-FtpTutorial-provide.zip{_}_"_
{info}
# Go in Petals Studio => _"Fast export for Petals"_ on the FTP SU.
# Drop the newly generated _sa-FTP-FtpTutorial-provide.zip_ from Eclipse to _./petals-platform-xxx/install/_
# Check in Petals ESB traces that the new SA was deployed sucessfully
# Test by calling DIR operation ob Webconsole
{info:title=Want to go further?}Try reading the files you listed. Look at the BC-FTP Documentation and go on your own. (note that your ftp session is read-only, if you want to call writing operations, create your own ftp server){info}
h2. Expose the FTP in SOAP
Before, we used SOAP to import WSDL to create services inside Petals ESB. Meaning _Provide_ a SOAP service inside the bus.
Now we will do the contrary : A service (FTP) exists inside the bus, we want to deploy it outside. The new SOAP service will _Consume_ the existing FtpTutorial. Then the goal of SOAP-consume is to expose as SOAP outside of the bus.
*Expose a SOAP-Consume of FtpTutorial*
# Petals Studio => File => New => Service Unit Project.
# Select: Consume / SOAP / Current_SOAP_Version
# Next: SOAP Service-Unit - You have to provide the namespace
# Clic "Select a service" => "FtpTutorial implements FtpInterface @ FtpTutorialEndpoint" => OK: Fields are automatically completed.
# Next: Define the project name and location
# Next: Define the specific properties for this version of the component
## Adress: *SoapFtpTutorial* (Name you want to give to the service)
# Next: Define the CDK properties
# Finish
# Export and deploy in Petals ESB
h2. Test with SOAP UI
*Install SOAP UI*
[Download SOAPUI|http://sourceforge.net/projects/soapui/] and install it. SOAP UI is a client to send and receive messages with SOAP protocol.
*Find the WSDL URL*
# You just deployed _sa-SOAP-FtpTutorial-consume_. Look at Petals ESB traces. Among the last messages, find one similar to the one following. And find the root URL, here "http://127.0.0.1:8084"
{code}[Petals.Container.Components.petals-bc-soap]-INFO 2010-10-06 15:26:22,032 The Axis2 service 'SoapFtpTutorial' has been registered and is available at 'http://127.0.0.1:8084/petals/services/SoapFtpTutorial'{code}
# Go to [http://127.0.0.1:8084] in your web browser
# Go to Service List
# Copy the SoapFtpTutorial WSDL URL
*Create a SOAP UI Project*
# Lauch SOAP UI
# File => New soapUI Project
## Project Name: PetalsFtpTutorial (or whatever name)
## Initial WSDL/WADL: \_Paste the WSDL URL previously copied. Might be: [http://127.0.0.1:8084/petals/services/SoapFtpTutorial?wsdl\_|http://127.0.0.1:8084/petals/services/SoapFtpTutorial?wsdl_]
# OK
*Test the proxified FTP DIR operation*
# PetalsFtpTutorial => FtpServiceSoapBinding => dir.
# Right clic on "Request1" => Show Request Editor: A window with a pre-generated messages appears
# Delete the optional part of the message ( <connection> node and its children)
{code:lang=xml|title=Your message looks like this}
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ver="http://petals.ow2.org/components/ftp/version-3">
<soapenv:Header/>
<soapenv:Body>
<ver:dir>
</ver:dir>
</soapenv:Body>
</soapenv:Envelope>
E-mail
...