Skip Navigation Links | |
Exit Print View | |
Oracle Java CAPS FTP Binding Component Tutorial Java CAPS Documentation |
Understanding the FTP Binding Component
Software Needed for the Tutorial
FTP Binding Component Project in a Nutshell
Starting the GlassFish Application Server
To Start the GlassFish Application Server
Working With JBI Runtime Environment
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 Operation Element (<ftp:operation>)
FTP Binding Element (<ftp:binding>)
FTP Transfer Element (<ftp:transfer>)
FTP Address Element (<ftp:address>)
FTP Message Element (<ftp:message>)
Creating a WSDL Document : Using FILE
To Create a WSDL Document : fileTrigger
To Add Web Services and Basic Activities
To Edit Web Service : Receive1
To Edit the Web Service : Invoke1
To Edit the Basic Activities : Assign1
Creating a Composite Application
To Create a Composite Application
Deploying the Composite Application
To Deploy the Composite Application
Working With Various Binding Types
To Add a Complex and a Global Complex Type to the XML Schema
The FTP Binding Component is bound to either a service consumer or service provider, and the exposed interfaces are defined by a WSDL document. The FTP Binding Component implements a set of extensibility elements specific to the FTP Binding Component so a service can be defined and bound to a FTP protocol.
The FTP Binding Component supports the following extensibility elements:
Address: The connectivity element information such as, FTP URL (host, port, login, password), directory listing style, and user defined heuristics for directory listing parsing.
Binding: A marker element indicating a FTP binding. This element does not have attributes.
Operation: A marker element indicating a FTP operation. This element does not have attributes.
Transfer: Specifies a message transfer from a sender and receiver perspective. For example, to specify a message transfer for a service request, there is a sender and a receiver involved and the WSDL document specifies the following:
The target sender sends to: Represented by the attribute ftp:sendTo (the target receiver receives from is represented by attribute ftp:receiveFrom). The additional operations performed before a message is sent (PUT) to target or after a message is received (GET) from the target are called Pre/Post operations.
messageCorrelate: If enabled, a UUID tagging-based message correlation scheme is used to correlate the request/response of a synchronous service.
Message: Specifies a message transfer from a service consumer or service provider perspective. The WSDL document can specify the following:
The message repository represented as the ftp:messageRepository attribute. A base directory where all the working directories for a message transfer are created, such as,
inbox: Used for posting requests (by consumer) and polling request (by provider).
instage: Used for staging requests.
outbox: Used for posting responses (by provider) and polling responses (by consumer).
outstage: Used for staging responses.
messageCorrelate: If enabled, a UUID tagging-based message correlation scheme is used to correlate the request/response of a synchronous service.
Note - Application Variable is a tabular data consisting of one or more name value pairs. On the other hand, WSDL authors are allowed to include references of these 'tokens' in the attributes values of FTP Binding Component extensibility elements in their WSDL, the references are resolved at deployment time.
Application variables are categorized into the following types:
STRING
BOOLEAN
NUMBER
PASSWORD