Oracle FTP Adapter File Listing Concepts

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. Oracle JCA Adapter for FilesFTP 4-73 ■ Fault-policies and fault-bindings must be created for remote faults to ensure that the adapter acts correctly. For more information on fault-policies and fault-bindings, see Section 2.22, Error Handling. ■ The MaxRaiseSize property must be set in the inbound JCA file.

4.4.2.2 High Availability in Inbound Operations

The Oracle File and FTP Adapters must ensure that only one node processes a particular file in a distributed topology. You can use the database table as a coordinator to ensure that Oracle File and FTP Adapters are highly available for inbound operations. Using Database Table as a Coordinator You must use the following procedure to make an inbound Oracle File or FTP Adapter service highly available by using database table as a coordinator:

1. Create Database Tables

You are not required to perform this step because the database schemas are pre-created as a part of soainfra.

2. Modify Deployment Descriptor for Oracle File Adapter

Modify Oracle File Adapter deployment descriptor for the connection-instance corresponding to eisHAFileAdapter from the Oracle WebLogic Server Administration Console: a. Log in to your Oracle WebLogic Server Administration Console. To access the console, navigate to http:servername:portnumberconsole.

b. Click Deployments in the left pane for Domain Structure.

c. Click FileAdapter under Summary of Deployments on the right pane.

d. Click the Configuration tab.

Note: For large payloads, you must increase the transaction time-out for the SOADataSource by adding the following: xa-set-transaction-timeouttruexa-set-transaction-timeout xa-transaction-timeout1000xa-transaction-timeout Note: For Windows platforms, you must ensure that the input and output directories are canonicalized. For example, you must use C:\bpel\input instead of c:\bpel\input. Note the use of capitalized drive letter C: instead of c:. Note: On all platforms, you must not end input or output directory names with the Java system property file.separator value. For example, tmpfilein is invalid but tmpfilein is valid. Note: You must increase global transaction timeouts if you use database as a coordinator.