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 WSDL Document : Using FILE

In this section, you add a WSDL document, the fileTrigger.wsdl, to the BPEL Module project. After adding the WSDL document, use the partner view of the WSDL editor to configure the components.

To Create a WSDL Document : fileTrigger

  1. Expand the SendInventory BPEL Module project node in the Projects tab.
  2. Right-click the project node or Process Files node. Point to New and select WSDL Document.
    image:File WSDL Document

    The ftpTransfer is one of the sub-nodes in the tree structure.

    The New WSDL Document wizard appears.

  3. In the File Name field, enter fileTrigger.wsdl.
  4. Select Concrete WSDL Document.
  5. In the Binding field, select FILE from the drop-down list.
  6. Choose any one of the following Types from the drop-down list.
    • Poll: Choose this type for a scenario when the File BC polls for messages from a file directory and invokes a JBI service with the messages.

    • Poll and Write Back Reply: Choose this type for a scenario when the File BC polls for messages from a file directory, invokes a JBI service, and writes the responses back to the directory.

    • Write: Choose this type for a scenario when a JBI service invokes File BC to write a message to a file directory.

    • On Demand Read: Choose this type for a scenario when a JBI service invokes File BC to read a specific message from a file directory.

  7. Select Poll from the Type drop-down list.
    image:File Poll Type
  8. Click Next.

    The New WSDL Document Request Configuration window appears.

  9. Enter the following fields:
    1. File Name* (pattern): Defines the file name relative to the specified directory.

      If fileNameIsPattern is not true, this attribute specifies an actual file name. Otherwise, this attribute specifies a pattern marker used for filtering input files from the directory, or a file name format to write to the directory. The supported patterns are:

      • %d: Denotes an unique number for input and an one-up sequence number for output file names.

      • %u: Denotes a wild card match for input and an UUID for output file names.

      • %t: Denotes an unique timestamp for both input and output file names. The expected date format is yyyymmdd-HH-mm-ss-SSS. For input file names, the -HH-mm-ss-SSS part may be omitted to guarantee unique names.

      • %{ }: Denotes an integer number in the input file name or a one up sequence number persisted in a sequence file if it is for a output file.

      For example, inventory%d.xml

    2. Polling Directory*: Defines the directory name where the WSDL provisioner reads the input files and where the client writes the files.

      For example, c:/temp.


    image:Request Configuration
  10. Click Finish.

    This action opens the Project tree structure. In the current example, the WSDL editor for fileTrigger is displayed along with its properties.


    image:File Trigger
  11. Click Save All.