Document Display https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-sta...

Setting up Archive Replication using the File System (Doc ID 445602.1)

In this Document

Goal
Solution
Overview of the Steps Needed
1. Setup a Share Directory
2. Create the Archive on the Source
3. Open the Source Archive on the Target System.
4. Importing the Archive on the Target
5. Setup Auto-Replication
6. Test the replication process
References

APPLIES TO:

Oracle WebCenter Content - Version 7.0.0 and later

Information in this document applies to any platform.
Checked for relevance on 22-OCT-2009
This process will work on any Content Server from version 3.6 to 11g
The Transfer and Replication process will work with/between any version of the Content Server

GOAL

This article provides instructions on how to setup Archive Replication between a Source System and a Target system using the File System
method of transfer.

This guide is geared toward Administrators who are beginners to advanced users.

SOLUTION

Archiver can transfer documents between two different Content Servers. These servers do not need to be the same version. The File
Transfer method is the easiest to setup and is also the most efficient because the batch file does not need to be broken down and sent
between the two servers. This method is ideal for large transfers where both the Source and Target systems can access the same share on
a file system.

Note: Use the CMU (Configuration Migration Utility) component to transfer the Content Server's metadata and layout. See
the product guides for information on CMU. The CMU utility can be used on Content Server version 5.0 and higher.

Definition of Source and Target:

The Source is the instance that the content is coming from, usually a production instance. An easy way to think of it is that the
Source has the information.
The Target is where the content will end up, usually a development or backup instance. The Target receives the information.

Before you begin:

When using Content Server version 6.x or higher the Source boxâÂÂs IP address needs to be listed on the Target boxâÂÂs
Security Filter, for example:

SocketHostAddressSecurityFilter=127.0.0.1|192.168.*.*

This can be done in the config.cfg file or by using the System Properties application. Consult the Content ServerâÂÂs Admin
guide for more information on this step.

If there are large archive with thousands of documents it is best to test/debug the process using a small archive that has less than

1 of 4 10/10/2016 9:56 AM
Document Display https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-sta...

100 documents in it. Once this process is working normally move on to the full archive.

The system times for the Source and Target Content Servers should be synchronized. This includes the time zones.

Archiver should be run as an application not an applet. To run as an application, start it from the Start/Programs/Stellent Content
Server/<instance>/Applications/Archiver menu or from the command line in Unix.

Overview of the Steps Needed

There are 6 steps to get the Archive Replication process running.

1. Setup a Shared directory.

2. Create an Archive on the Source and perform an Export.
3. Open the Archive created in step 2 on the Target system.
4. Importing the Archive on the Target.
5. Setup Replication.
6. Test the replication process.

1. Setup a Share Directory

The share must be accessible by both Content Servers. The Source Content Server must have Write Permissions, the Target Must have
Read and Delete Permissions. This share can be on either Content Server, a NAS, or any network share.

The Content Server Service must be running as a Domain Admin or it must be running as a user that has permissions to run both Content
Servers. If this is not setup properly the Import will not run automatically. You can test to see if this is the problem by running the Content
Server from the Command line. (See the Install Guide or the Administration Guide for more information.)

<install dir>/bin/IdcServer.exe -console

Note that if this is a network drive the exports process might take longer.

The Archive files are written into the Archive directory of the system. By default this is the <install dir>/archive.

This is the directory that should be shared.

This directory can be changed by using a config entry on the source system. You do not need to add the entry on the target system.

CollectionLocation Defines where the default Archive collection is located.

Example: CollectionLocation=C:/Oracle/new/archives/

This directory must exist, the system will not create this directory.

2. Create the Archive on the Source

On the Source box start the Archiver as an application using Start/Program Files/Content Server/<Instance name>/Applications/Archiver.
Login with a user that has Admin rights.

a. Make sure you have the local collection selected:

Go to the Options menu select Open Archive Collection

Choose the local collection. (Probably already selected)

b. Create a new Archive on SOURCE:

Select the Edit menu then Add to add the new archive

2 of 4 10/10/2016 9:56 AM
Document Display https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-sta...

Enter the Archive Name

Enter a Description.

c. Set the criteria for the query:

Select the Export Data Tab. If you are doing a full export you do not need to enter any information in this field. It will export
everything.
On the Query screen check the box for Export Revisions with Release Date later than most recent Export to create an
incremental export.

d. Export the Archive.

From the Actions menu select Export

3. Open the Source Archive on the Target System.

Open the Archiver on the Target box from the menu (on windows) Start/programs/Stellent Content Server/<instance>/Archiver

On UNIX use the command line.

a. Open the Local collection on the shared file system.

Go to the Options menu and select Open Archive Collection

Press the Browse Local button
Navigate to where the Source ArchiveâÂÂs collection.hda file was saved in step 2 and press OK
A new window will pop up titled Browse To Archiver Collection
Enter the Web Directory path and the Vault Directory path. The Web Directory is the path to the Weblayout directory on the Target
system. Usually <install dir>/weblayout. The Vault Directory is the path to the Vault directory on the Target system. Usually
<install dir>/vault

If there is already a source collection in the list of collections on the target, it needs to be removed. Otherwise if you then select the
collection.hda from the source, it will give the error 'A colection with this name already exists in the system'. That collection could be there
from a previous push or pull archive.

4. Importing the Archive on the Target

Now the Archive is connected you need to import the information manually. This step is done on the Target system

Note: If the metadata fields do not match between servers you will need to use Field Mapping on the Import Maps
Tab.

a. With the correct archive selected, select Actions then Import from the Archiver menu

b. Click OK.

The status bar will indicate Finished when done

5. Setup Auto-Replication

Turn on Auto-Replication once the initial Export and Import steps have been completed. After you turn this on, any documents checked into

3 of 4 10/10/2016 9:56 AM
Document Display https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-sta...

the Source that matchs the criteria for the Archive will automatically be transferred to the Target system

a. On the Source system, click the Replication tab and in the Registered Exporters section click the Edit button:

b. Check the box for Enable Automated Export.

c. Click the Register button to register the Source instance as an exporter

d. Click OK to close the window

On the Target System

a. On the Replication tab and in the Registered Importer section click the Register Self button. A message box will pop up,
select OK to close that window.

6. Test the replication process

On the Source check-in a new document that matches the Archive Export criteria. Within a few minutes that document should be
transferred to the Target. It can take a while for this document to make it over because it has to go through the standard check-in process
on two different content servers. A very broad overview of the process goes something like this:

Check in
PDF Converter
Index on Source
Release on Source
Create archive batch file
Import on Target
Index
Release on Target

REFERENCES

NOTE:445601.1:445600.1
Didn't find what you are looking for?

4 of 4 10/10/2016 9:56 AM