Oracle FTP Adapter Synchronous Get File Concepts

Oracle JCA Adapter for FilesFTP 4-71 Figure 4–41 Selecting the Synchronous Get File Operation

4.3.8 Oracle FTP Adapter File Listing Concepts

The Oracle FTP Adapter file listing concepts are similar to the Oracle File Adapter file listing concepts discussed in Section 4.3.4, Oracle File Adapter File Listing Concepts. The Oracle FTP Adapter polls for files in a target directory and lists files from the target directory to specified FTP locations. The contents of the files are not read. This feature of the Oracle FTP Adapter lets you use an invoke activity to retrieve a list of files from a target directory. This list of files is returned as an XML document and contains information such as file name, directory name, file size, and last modified time. You use the Adapter Configuration Wizard to configure the Oracle FTP Adapter for use with a BPEL process or a Mediator service. This creates an outbound WSDL and JCA file pair. For listing files, you must select the List Files operation from the Operation Type page of the Adapter Configuration Wizard. In the File Directories page of the Adapter Configuration Wizard, you must specify information about the directory to use for reading file names for the list operation. You can choose to list files recursively within directories. The File Filtering page of the Adapter Configuration Wizard enables you to specify details of the files to retrieve or ignore. The Oracle FTP Adapter acts as a listener and polls the specified directory on a local or remote file system and looks for files that match specified naming criteria. Note: The file creation time property, creationTime, is not supported for FTP because the standard Java APIs do not provide a mechanism to retrieve the creation time. The value of the creationTime property is always displayed as 0. The creationTime property is supported for SFTP only. 4-72 Oracle Fusion Middleware Users Guide for Technology Adapters

4.4 Configuring Oracle File and FTP Adapters

Various configuration tasks for Oracle File and FTP Adapters are discussed in the following sections: ■ Section 4.4.1, Configuring the Credentials for Accessing a Remote FTP Server ■ Section 4.4.2, Configuring Oracle File and FTP Adapters for High Availability ■ Section 4.4.3, Using Secure FTP with the Oracle FTP Adapter ■ Section 4.4.4, Using SFTP with Oracle FTP Adapter ■ Section 4.4.5, Configuring Oracle FTP Adapter for HTTP Proxy

4.4.1 Configuring the Credentials for Accessing a Remote FTP Server

To access a remote FTP server, you must configure the following credentials: ■ User name: the user name to use on the remote FTP server. ■ Password: the password to use on the remote FTP server. ■ Port: 21 ■ Host: the IP address of the remote FTP server. You must configure these credentials by modifying the weblogic-ra.xml file using the Oracle WebLogic Server console. To do so, in the Oracle WebLogic Server Admin Console:

1. Select Deployments from the Navigation pane on the left.

2. Select FtpAdapter from the table of Deployments shown on the right.

3. Select the Configuration subtab for the FtpAdapter and then Outbound

Connection Pools . 4. Expand javax.resource.cci.ConnectionFactory and then select the instance that you are modifying. For example, choose the eisFtpFtpAdapter instance for the non-HA use case.

4.4.2 Configuring Oracle File and FTP Adapters for High Availability

The requirements and procedure to configure the Oracle File and FTP Adapters for high availability for an active-active topology are discussed in the following sections: ■ Section 4.4.2.1, Prerequisites for High Availability ■ Section 4.4.2.2, High Availability in Inbound Operations ■ Section 4.4.2.3, High Availability in Outbound Operations

4.4.2.1 Prerequisites for High Availability

Before you configure the Oracle File or FTP Adapter for high availability, you must ensure that the following prerequisites are met: ■ Clustered processes must use the same physical directory. ■ Connection-factories must specify the same shared directory as the control directory, and their names must match. For example, if the deployment descriptor for one connection factory has sharedcontrol_dir as the value for controlDir, then the other deployment descriptor must also have the same value.