Ucm Archive Pull Replicate
Ucm Archive Pull Replicate
Ucm Archive Pull Replicate
In this Document
Goal
Solution
Before starting:
Overview of the Steps Needed
1. Setup an outgoing provider on the Target System
2. Create the Archive on the Source System
3. Create the Archive on the Target System
4. Perform an initial Export and Transfer
5. Importing the Archive on the Target
6. Setup Auto-Transfer
7. Test the replication process
References
APPLIES TO:
GOAL
This article provides instructions on how to setup Archive Replication between a Source System and a Target system using the Pull method of transfer.
This guide is geared toward Administrators who are beginners to advanced users.
SOLUTION
This guide is used to setup up replication between two Content Server instances using the Archive Transfer agent. The pull method is preferred when the Source or Target are
clustered or when the network environment dictates. The replication process will work between Content Servers that are different versions.
Note: Use the CMU (Configuration Migration Utility) component to transfer the Content Server's metadata and layout. See the product documentation for
more information on CMU. CMU will work on Content Server version 5.0 and higher.
1 of 13 6/13/2014 4:21 PM
Document 445601.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12cr8qt1n8_4&id=44...
The Source is the instance where 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 starting:
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 is a large archive with thousands of documents in it, test/debug the process using a small archive that has less than 100 documents in it first. Once that 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.
The system times for the Source and Target should be synchronized. This includes the time zone setting.
There are 7 steps to get the Archive Replication process running. If you are not going to use the Auto Replication feature you only need to complete steps 1 - 5.
Create an outgoing Provider on the Target System. No provider is needed on the Source System. It almost seems counter intuitive to setup an outgoing provider for a pull
operation. Think of it this way - the provider will be going out to the Source box to gather the information.
b) Under the Action column click Add for the Provider Type of outgoing:
2 of 13 6/13/2014 4:21 PM
Document 445601.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12cr8qt1n8_4&id=44...
The rest of the information is gathered from the config.cfg file on the Source System. This file is located in the <stellent>/config folder. The names below are only
an example. do not include the words shown in the parentheses.
Do not change anything below Relative Web Root. Leave the Server Options, Search Options, Required Roles and Account Filter blank.
The following screen shot shows how it should look once finished
Figure 1-1
3 of 13 6/13/2014 4:21 PM
Document 445601.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12cr8qt1n8_4&id=44...
4 of 13 6/13/2014 4:21 PM
Document 445601.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12cr8qt1n8_4&id=44...
e) From the Administration page go to the Admin Server then stop and start the Source Server.
f) Go back to the provider page and under the Providers section click the Test link next to the provider you just created.
Figure 1-2
Note: For 11g systems you will need to add a configuration entry into your <install dir>/domain/ucm/cs/config/config.cfg file
IntradocServerPort=4444 (Use any open port on the system, 4444 is the default port for10g.)
You will need to restart the system for the change to take effect.
Create the Archive on the Source System first. Now is a good time to check the SocketHostAddressSecurityFilter listed in the beginning of this document to make sure it includes
the IP address of the Target System.
This step should be done using the Archiver application on the Source System.
Select the Edit menu then Add - add the new archive:
Figure 2-1
5 of 13 6/13/2014 4:21 PM
Document 445601.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12cr8qt1n8_4&id=44...
Ensure the newly created archive is highlighted in the list of Current Archives.
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 System for Export Revisions with Release Date later than most recent Export to create an incremental export.
On the Target System start the Archiver as an application using Start/Program Files/Stellent Content Server/<Instance name>/Applications/Archiver or from the command line
if you are using a UNIX system. Login with a user that has Admin rights.
Select the Edit menu then Add to add the new archive:
Figure 3-1
6 of 13 6/13/2014 4:21 PM
Document 445601.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12cr8qt1n8_4&id=44...
Enter the Archive Name. This name should be the same as the one that you created on the Source.
Enter a Description.
c. Select the Transfer To tab in the Transfer Options choose the Edit button.
d. While you are still on the Target System Archiver open up the Source Archive.
Figure 3-2
Figure 3-3
7 of 13 6/13/2014 4:21 PM
Document 445601.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12cr8qt1n8_4&id=44...
Note: If the Source Collection does not show up, close the Archiver applications on both system and then restart both content servers. If it still does not
show up double check the Provider on the Target box.
Figure 3-4 shows a representation of what Archiver should look like when finished. Notice the Archive application is open on the Target system by looking at the title bar. In this
case it reads Archive for Target75, the name of the Target Archive Collection.
In the Current Archives section notice that the Source Collection is opened and a list of Archives on the Source System is visible.
On the Archive Selection window the Replication Archive located on the Source System is selected.
It is important to do this step from the Target System because it will make the Target System the Owner of the Archive. This step is what differentiates a Pull from a Push style
Archive.
Figure 3-4
8 of 13 6/13/2014 4:21 PM
Document 445601.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12cr8qt1n8_4&id=44...
e. Select the Transfer To tab, in the Transfer Destination section click the Edit button.
Figure 3-5
9 of 13 6/13/2014 4:21 PM
Document 445601.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12cr8qt1n8_4&id=44...
f. Highlight the Target Instance in the Collections window then select the Target archive in the Archives window.
g. Click OK.
The Export will create the Archive batch file and the Transfer will copy it over to the Target System. This step is done on the Source System using the Source Archive.
a. On the Source System make sure you have the Source Collection selected.
d. The Export Archive window will pop up asking if you want to delete revision after successful archive. Make sure this box remains unchecked.
Figure 4-1
e. Click OK to close this window. The status bar will indicate Finished when it's done creating the Archive. The progress of the archive is reported in percentage completed
10 of 13 6/13/2014 4:21 PM
Document 445601.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12cr8qt1n8_4&id=44...
The next step must be done on the Target System using the Source Archive.
b. From the menu select Actions then Transfer to move the archive to the Target. The progress of the transfer is reported in percentage complete in the bottom of the
Archive window.
Now that the information is on the Target System you need to Import the information into the Content Server.
Note: If the metadata fields do not match between servers you will need to use Field Mapping on the Import Maps Tab.
This step must be done from the Target System using the Target Archive.
c. Click OK.
The status bar will indicate Finished when the process is done.
6. Setup Auto-Transfer
You can only turn on Auto-Replication once the initial Export, Transfer and Import steps have been completed successfully. After you turn this on any documents checked into
the Source that match the criteria for the Archive will automatically be sent to the Target.
This step must be done one the Source System using the Source Archive.
b. Select the Replication tab and in the Registered Exporters section click the Edit button.
Figure 6-1
11 of 13 6/13/2014 4:21 PM
Document 445601.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12cr8qt1n8_4&id=44...
This next step must be done on the Target System with the Source Archive open.
a. Using Archiver on the Target system, make sure you have the Source collection selected.
b. Select the Transfer To tab then in the Transfer Options section click the Edit buttons.
This next step must be done on the Target System with the Target Archive open.
a. Using Archiver on the Target system, make sure you have the Target Collection selected.
b. On the Replication tab in the Registered Importer section click the Register Self button. A message box will pop up, select OK to close that window.
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 broad overview of the process goes something
12 of 13 6/13/2014 4:21 PM
Document 445601.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=12cr8qt1n8_4&id=44...
like this:
Check in on Source
PDF Converter
Index
Release on Source
Create archive batch file on Source
Transfer Batch to Target CS
Import on Target
Index
Release on Target
Note: Replication uses a zip utility to compress the files during the transfer. That zip utility is a 32 bit application. Because of this archives that are larger than 4GB will cause
problems. If the initial export is larger then 4GB, it would need to be broken up into smaller, separate archives.
REFERENCES
13 of 13 6/13/2014 4:21 PM