7.7 Transferring Files

The Transfer function is used to move or copy content from one content server to another over sockets.

• "File Transfer Overview"

• "Transfer Types"

• "Transferring Batch Files"

• "Managing Transfers"

7.7.1 File Transfer Overview

You can use the Transfer function to transfer files between content servers on a shared file system, but transfers do not require a shared file system. Transferring files between non-shared file systems requires an outgoing provider on the source content server instance.

Transfers will be successful only between Content Server 4.5 or newer systems.

Caution: Archiver cannot be used to move or copy data between two instances that share the same content server instance name (IDC_Name). To do so will corrupt the data on the target system.

This section covers these topics:

• "Transfer Uses"

• "Transfer Methods"

• "Transfer Terms"

7.7.1.1 Transfer Uses

Typical uses for the Transfer function include:

• Exporting and importing over a firewall.

  
  

  Note: To transfer across a firewall, you might need to configure the firewall to permit the outgoing provider's socket to pass through it.

  
  

• Transferring content between content server instances in different physical locations (buildings, cities, or countries).

• Transferring content between content server instances using a shared drive. (A transfer over a file system share can handle large archives better than a socket transfer.)

• Avoiding the need to build an FTP or HTTP interface to move files from one file system to another.

• Combining the batch files from two archives into a single archive.

7.7.1.2 Transfer Methods

You can transfer files in the following ways:

• Manual Transfer: A one-time transfer initiated from Archiver by an administrator. This copies an archive to another archive.

• Automatic Transfer: Moving archive files to another archive is initiated automatically whenever the source archive is updated.

7.7.1.3 Transfer Terms

The following terms are related to the Transfer function:

• local archive: An archive that belongs to a local collection.

• local collection: A collection that the content server can reach by file access using a mapped or mounted network share.

• local transfer: A transfer between local archives. Both the source archive and the target archive are in a local collection.

• proxied: In Archiver, the term 'proxied' refers to any content server to which the local content server is connected through an outgoing provider.

• proxied archive: An archive that belongs to a proxied collection.

• proxied collection: A collection on another content server that the local content server can reach through an outgoing provider.

• pull transfer: A transfer over an outgoing provider that is owned by the proxied (remote) content server.

• push transfer: A transfer over an outgoing provider that is owned by the local content server.

• source archive: An archive that contains batch files to be transferred.

• target archive: An archive that receives transferred batch files.

• targetable archive: An archive that is enabled to be a target archive.

• transferring: The process of copying or moving batch files and their associated content files from one archive to another. There are three types of transfers: local, push, and pull.

• transfer owner: The content server instance that performs and monitors a transfer.

• transfer source: See source archive.

• transfer target: See target archive.

7.7.2 Transfer Types

This section provides information about the different transfer types, listed in order from simplest to most complex.

• "Local Transfer"

• "Pull Transfer"

• "Push Transfer"

7.7.2.1 Local Transfer

A local transfer is a transfer between local archives, which belong to collections that both the source and target content servers can reach through a mapped or a mounted drive. An outgoing provider is not required. This type of transfer is typically used to combine the batch files of two archives.

Note: If you are transferring between content servers on a shared file system, the mapped or mounted drive must be available to both content servers. The computers must be on and logged in as a user who has system access to both content servers.

Figure 7-16 Local Transfer

Description of "Figure 7-16 Local Transfer"

7.7.2.2 Pull Transfer

A pull transfer is a transfer that is owned by the proxied (remote) content server, which is the instance that is the target of the outgoing provider.

• Multiple pull transfers can be concurrent.

• If you are running a pull transfer across a firewall, you might need to configure the firewall to permit the outgoing provider's socket to pass through it.

  
  

  Note: In Archiver, the term 'proxied' refers to any content server to which the local instance is connected through an outgoing provider. This does not have to be a proxied instance of the master content server.

  
  

Figure 7-17 Pull Transfer

Description of "Figure 7-17 Pull Transfer"

7.7.2.3 Push Transfer

A push transfer is a transfer that is owned by the local content server, 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) content server back to the source (local) content server. This 'talkback' provider can then notify the source content server when each transfer is complete. A push transfer will work without the talkback provider, but the source content server 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 7-18 Push Transfer

Description of "Figure 7-18 Push Transfer"

7.7.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 content server 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 content server. For a manual transfer, the batch files and associated content files remain in the source content server.

   The transferred archive is now available for import through the Archiver of the target content server.

Figure 7-19 The Transfer Process

Description of "Figure 7-19 The Transfer Process"

Transfer Rules

The following list provides applicable transfer rules:

• If you are transferring between content servers on a shared file system, the mapped or mounted drive must be available to both content servers. The computers must be on and logged in as a user who has system access to both content servers.

• The content server that has an outgoing provider set up is considered the 'local' server, and the target content server 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 a content server, 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 content servers that is owned by a third content server.

• 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.

7.7.4 Managing Transfers

This section provides information about managing transfers.

• "Transfer Process"

• "Making an Archive Targetable"

• "Defining an Outgoing Transfer Provider"

• "Setting a Transfer Destination (Target)"

• "Initiating a Manual Transfer"

• "Deleting a Transfer"

7.7.4.1 Transfer Process

To transfer content between content servers:

1. In the source content server, create the archive to be transferred and set up an export to this archive. See "Manually Exporting".

2. In the target content server, create the archive to receive transferred content and make the target archive 'targetable.' See "Making an Archive Targetable".

3. Set up communications between content servers:

   • If the source and target archives are on a shared file system, ensure that both computers are on and logged in as a user who has system access to both content servers.

   • If the source and target archives are not on a shared file system, create an outgoing provider from the source content server to the target content server. See "Defining an Outgoing Transfer Provider".

4. From the source archive, specify the target archive. See "Setting a Transfer Destination (Target)".

5. Initiate the transfer. See "Initiating a Manual Transfer".

   The batch files and content files are copied to the target archive.

7.7.4.2 Making an Archive Targetable

To indicate that an archive can receive transfers from other archives:

1. Open the archive collection that contains the target archive. See "Opening a Collection".

2. Select the target archive in the Current Archives list.

3. Click the Main Archiver Transfer Screen.

4. Click Edit in the Transfer Options section.

   The Transfer Options Screen is displayed.

5. Select the Is Targetable check box.

6. Click OK.

7.7.4.3 Defining an Outgoing Transfer Provider

To create an outgoing provider for transfer purposes:

1. On the source content server, create an outgoing provider. Enter the following information:

   Field	Description
   Provider Name	Enter a name. This will become a subdirectory in the DomainHome/ucm/cs/data/providers/ directory.
   Provider Description	Enter a user-friendly description, such as Transfer Provider.
   Server Host Name	Enter the server host name of the target content server. For example, extranet_server.
   Server Port	Enter a unique port number on which the provider will communicate with the target content server.
   Instance Name	Enter the name of the target content server instance. For example, Master_on_extranet.
   Relative Web Root	Enter the relative web root of the target content server instance. For example, /stellent/.
   Proxied check box	Select this check box only if the target content server was installed as a proxy of the local (master) content server. See the Caution message below.

   
   
   
   

   Caution: Do not select this check box if the relative web root is the same for both content servers.

   
   

2. In the System Properties utility of the target content server, set the IP Address Filter or Hostname Filter to the IP address or host name of the source content server. (The IP Address Filter setting is recommended.)

3. If you are setting up a push transfer (transfer owned by the local content server), consider setting up a 'talkback' outgoing provider from the target content server back to the source content server.

4. If you are transferring across a firewall, configure the firewall to permit the outgoing providers' sockets to pass through it.

7.7.4.4 Setting a Transfer Destination (Target)

To specify the target archive to receive transferred content:

1. Open Archiver from the content server that will own the transfer.

   • For a pull transfer, the transfer owner is the target (proxied) content server.

   • For a push transfer, the transfer owner is the source (local) content server.

2. Open the archive collection that contains the source archive. See "Opening a Collection".

3. Select the source archive in the Current Archives list.

4. Click the Main Archiver Transfer Screen

5. Click Edit in the Transfer Destination section.

   The Archive Collections Screen is displayed.

6. Select the collection that contains the target archive.

7. Select the target archive.

   
   

   Note: The target archive must be identified as targetable. See "Making an Archive Targetable".

   
   

8. Click OK.

7.7.4.5 Initiating a Manual Transfer

To transfer content manually:

1. Open Archiver on the source content server.

2. Open the archive collection that contains the source archive. See "Opening a Collection".

3. Select the source archive in the Current Archives list.

4. Select Actions, and then click Transfer.

   The transfer process is initiated, and the status bar at the bottom of the Archiver screen displays progress messages.

7.7.4.6 Deleting a Transfer

This section provides information about the methods to delete a transfer.

Deleting a Transfer from the Transfer To Tab

To delete a transfer using this method:

1. Open the archive collection that contains the source archive. See "Opening a Collection".

2. Select the source archive in the Current Archives list.

3. Click the Main Archiver Transfer Screen.

4. Click Remove in the Transfer Destination section.

   You are prompted to confirm the action.

5. Click Yes.

Deleting an Automated Transfer from the Automation for Instances Screen

To delete a transfer using this method:

1. Open the archive collection. See "Opening a Collection".

2. Select Options, and then click View Automation For Instance.

   The Automation Screen is displayed.

3. Click the Transfers tab.

4. Select the automated transfer to delete.

5. Click Remove.

   The automated transfer is removed from the list.