Transferring Batch Files Transferring Files

Managing System Migration and Archiving 8-47 Figure 8–17 Pull Transfer

8.6.2.3 Push Transfer

A push transfer is a transfer that is owned by the local Oracle Content Server instance, which is the instance on which the outgoing provider is set up. ■ For performance monitoring of a push transfer, you also should set up an outgoing provider from the target proxied Oracle Content Server instance back to the source local Oracle Content Server instance. This talkback provider can then notify the source Oracle Content Server instance when each transfer is complete. A push transfer will work without the talkback provider, but the source Oracle Content Server instance would not be aware of transfer completion or problems. ■ Only one push transfer can be in progress at a time. ■ If you are running a push transfer across a firewall, you might need to configure the firewall to permit the both providers sockets to pass through it. Figure 8–18 Push Transfer

8.6.3 Transferring Batch Files

This section provides information about transferring batch files. Transfer Process When a transfer is initiated, the following actions occur: 1. Each batch file in the archive is zipped together with its associated content files. 2. The Zip files are transferred to the target Oracle Content Server instance by a local file system move local transfer or by the outgoing provider push or pull transfer. 3. The Zip files are unzipped and placed in the appropriate file system locations. 4. For an automated transfer, the batch files and their associated content files are removed from the source Oracle Content Server instance. For a manual transfer, 8-48 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server the batch files and associated content files remain in the source Oracle Content Server instance. The transferred archive is now available for import through the Archiver of the target Oracle Content Server instance. Figure 8–19 The Transfer Process Transfer Rules The following list provides applicable transfer rules: ■ If you are transferring between Oracle Content Server instances on a shared file system, the mapped or mounted drive must be available to both Oracle Content Server instances. The computers must be on and logged in as a user who has system access to both Oracle Content Server instances. ■ The Oracle Content Server instance that has an outgoing provider set up is considered the local server, and the target Oracle Content Server instance for the outgoing provider is considered the proxied server. Files are always transferred in the direction of the outgoing provider, from the local source instance to the proxied target instance. ■ To transfer multiple archives from an Oracle Content Server instance, you must set up a separate outgoing provider from the local instance for each target instance. ■ Only archives that are identified as targetable can be transfer targets. When you are selecting a transfer target, the targetable attribute can help you find the target archive quickly. ■ At least one archive in the transfer must be local to the transfer owner. For example, you cannot set up a transfer between two Oracle Content Server instances that is owned by a third Oracle Content Server instance. Managing System Migration and Archiving 8-49 ■ An archive can contain only one copy of each batch file. Therefore, if a batch file being transferred already exists in the target archive, the batch file and its associated content files will be ignored.

8.6.4 Managing Transfers