JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Java CAPS FTP Binding Component Tutorial     Java CAPS Documentation
search filter icon
search icon

Document Information

Understanding the FTP Binding Component

Tutorial Overview

Tutorial Requirement

Software Needed for the Tutorial

Tutorial Plan

FTP Binding Component Project in a Nutshell

Starting the GlassFish Application Server

To Start the GlassFish Application Server

Working With JBI Runtime Environment

To Start JBI Components

FTP Binding Component Runtime Configuration Properties

Creating a BPEL Module Project : SendInventory

To Create a BPEL Module Project

Creating a WSDL Document : Using FTP

To Create a WSDL Document : ftpTransfer

To Modify ftp:message Properties

Poll Request Wizard Properties

FTP MessageActivePassive Element (<ftp:messageActivePassive>)

FTP Binding Component Extensibility Elements

Runtime Configuration

FTP Operation Element (<ftp:operation>)

FTP Binding Element (<ftp:binding>)

FTP Transfer Element (<ftp:transfer>)

Pattern Matching

FTP Address Element (<ftp:address>)

FTP Message Element (<ftp:message>)

Creating a WSDL Document : Using FILE

To Create a WSDL Document : fileTrigger

Creating a BPEL Process

To Create a BPEL Process

To Add a Partner Link

To Add Web Services and Basic Activities

To Edit Web Service : Receive1

To Edit the Web Service : Invoke1

To Edit the Basic Activities : Assign1

Validating BPEL

To Invoke Explicit Validation

Design View : Notifications

The Design View

Creating a Composite Application

To Create a Composite Application

Deploying the Composite Application

To Deploy the Composite Application

Working With Various Binding Types

Exploring the XML Schema

About the Schema View

Creating the XML Schema

To Create XML Schema

To Add a Complex and a Global Complex Type to the XML Schema

To Add Element to the XML Schema

To Add Elements to the XML Schema

Creating a Composite Application

Add the JBI module to the BPEL Module project before deploying the Composite Application. Deploying the project makes the service assembly available to the application server, thus allowing its service units to execute.

To Create a Composite Application

  1. Choose File —> New Project from the main menu.

    The New Project wizard appears.

  2. Select the SOA node from the Categories list.
  3. Select the Composite Application node from the Projects list.
  4. Click Next.
    image:Composite Application
  5. Type SendInventoryCompAppl in the Project Name field.
  6. Click Finish.

    The Projects window now contains a project node for a Composite Application project called SendInventoryCompAppl.


    image:Composite Application XML

    This action displays a message in the Output console.

    XML validation finished
  7. Either right-click the SendInventoryCompAppl Composite Application Project node or expand the node. Select JBI Modules.
  8. Select Add JBI Module.
  9. Select the Project. Click Add Project JAR Files.

    The Project JAR Files is build/SEDeployment.jar.


    image:Add JAR File

    The SendInvetory.jar is added to the project.

  10. Click Save All.
    image:JAR File Involved
  11. Right-click the SendInventoryCompAppl Composite Application project node. Select Clean and Build.
    image:Clean and Build

    This action displays a message in the Output console:

    BUILD SUCCESSFUL (total time: 1 seconds)
  12. Click Save All.

Deploying the Composite Application

The File Binding Component picks up messages from a local directory. The FTP Binding Component transports messages between the consumer and the provider using FTP.

To Deploy the Composite Application

  1. Create a folder and save the file in the local directory.

    For example, use a folder name of c:/temp and file name of inventory%d.xml.


    image:Inventory Folder
  2. Create a folder on the FTP Server named book_updates.

    The folder is empty before deployment.


    image:book updates
  3. Select the SendInventoryCompAppl project node in the Projects window.
  4. Right-click and choose Deploy.
    image:Deployment successful

    After deployment of the project, the following message appears in the Output window:

    BUILD SUCCESSFUL (total time: 18 seconds)
  5. Check for the folder in the local directory.

    Two folders are created under SendInventoryCompAppl_FileInboundService_fileTrig-45609436–4:

    1. archive
    2. filebc-in processing
      image:Input File
  6. Check the folders on the FTP Server.

    After deployment, inbox and instage folders are created.


    image:Folders created
  7. Double-click the folder /inbox to check the output.

    The message routing starts with the consumer invoking a service (INVOKE in BPEL script). On the other side of the NMR, FTP BC OutboundProcessor accepts the request message, de-normalizes the message and labels the message body (which is the payload to a FTP file) with name as req.


    image:req Name conventions