Once a production environment is fully set up and functional, it becomes necessary to have a mirror environment where further testing/component deployment/performance tuning steps and monitoring can be done. Exporting the content from a Production environment to a lower one is necessary. This article gives a very easy mechanism to move archive collections for such scenarios, which administrators can leverage for quick turnaround. The steps listed here presume that the export collection has been created and the items exported on the source server.

On Source WebCenter Content:

1. From Admin Applets – Archiver – note the export collections (and if there is any description set for it) which need to be moved.

2. Navigate to <WCC_Domain_home>/ucm/cs/archives directory and open collection.hda file.

3. The file structure would be like this:

<?hda jcharset=”UTF8″ encoding=”utf-8″?>
@Properties LocalData
IDC_Name=SourceServer
blDateFormat=M/d{/yy}{ h:mm[:ss]{ a}}!mAM,PM!t<Time Zone>
@end
@ResultSet Archives
2
aArchiveName
aArchiveDescription
ExportCollection1
This is a test Collection
ExportCollection

@end

Note the difference in entries for the collections named ExportCollection1 and ExportCollection2. For ExportCollection2, no description is defined, hence the space after the name and before the end. For ExportCollection1, the description is defined on the server, hence the value is listed here.

4. From this file, copy the list of collections which need to be moved and the Name – Description pair has to be copied exactly as is.

5. Under the same directory there will be 2 subfolders with the following names:

ExportCollection1
ExportCollection2

These are the actual export collections which have the contents and all the associated entities.

On Target Server:

6. Like in Step 2, open collection.hda and paste the values copied in Step 4, such that the existing values are not overwritten.

For example, existing collection.hda entries on target is:

<?hda jcharset=”UTF8″ encoding=”utf-8″?>
@Properties LocalData
IDC_Name=TargetServer
blDateFormat=M/d{/yy}{ h:mm[:ss]{ a}}!mAM,PM!t<Time Zone>
@end
@ResultSet Archives
2
aArchiveName
aArchiveDescription
TargetCollection1
This is a test Collection
TargetCollection2

@end

After pasting the new set of entries copied from Source server, the new file will be as follows:

<?hda jcharset=”UTF8″ encoding=”utf-8″?>
@Properties LocalData
IDC_Name=TargetServer
blDateFormat=M/d{/yy}{ h:mm[:ss]{ a}}!mAM,PM!t<Time Zone>
@end
@ResultSet Archives
2
aArchiveName
aArchiveDescription
TargetCollection1
This is a test Collection
TargetCollection2

ExportCollection1
This is a test Collection
ExportCollection2

@end

Note the space after TargetCollection2. There is no description added for this collection, hence the blank has to be retained like that.

7. Copy the entire subfolders from Step 5 to /archives location on the target folder.

8. Now, the collection.hda file is set up with new export entries and the corresponding collection folders have been copied as well.

9. Launch the Archiver applet from Admin applets or as Stand-alone and verify the new collections are listed.

10. Select each of the new collections and open them to ensure they are fully accessible.

11. Now, each of these collections can be selected and Import action run to have the items checked in to target server.

These steps show how to skip Archiver to Archiver communication setup to move content items in bulk from one environment to other. This is not a replacement for Auto Replication set up, where every time a new content/folder is checked in/created/deleted/removed, the same action is replicated in target server.

If you’d like more help successfully and efficiently using your Oracle WebCenter environment to transform your business, contact our experienced Oracle consultants here so we can assist you today!