Adding Content ID Prefixes Changing Release Dates

8-66 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server

2. Select the target archive and ensure that the Update Override Action is set on the

General tab. 3. Import the target archive manually. 4. On the Replication tab, register the archive as an automated importer. Set up an automated pull transfer from the Contribution server to the HR Portal server: 1. On the Contribution Oracle Content Server instance, create an outgoing provider to the HR portal Oracle Content Server instance.

2. Open Archiver on the HR portal Oracle Content Server instance.

3. Open the target collection and make the target archive targetable. 4. Open the source collection and select the source archive. 5. On the Transfer To tab, select the target archive as the target destination. 6. Run a manual transfer. 7. Set the transfer to be automated.

8.8.7.3 Changing Metadata Fields

In this example, you have a custom metadata field, ApprovedBy, which was used in one Oracle Content Server instance, but the field name must be changed to Sponsor for consistency with other Oracle Content Server instances.

1. Create the new Sponsor metadata field.

2. Create an archive.

3. Manually export all content to the archive. You do not need to create an export

query.

4. Set up the following import field map for the archive:

5. From the General tab, select Update as the Override Action.

6. Initiate the import manually. 7. Delete the ApprovedBy field from the Oracle Content Server instance.

8.8.7.4 Adding Content ID Prefixes

In this example, you have two Oracle Content Server instances that are used as contribution servers, but you want to have all content available for consumption from both servers. You can set up an automatic transfer in both directions. However, both Oracle Content Server instances use automatic Content ID generation with similar numbering schemes, which could result in errors or overwritten revisions if you import files with Content IDs that already exist on the target Oracle Content Server instance. ■ One way to avoid conflicts is to add a unique prefix in the Auto Number Prefix system property on both Oracle Content Server instances. ■ Another way to accomplish this is to add a unique prefix during the import process: Export Field Target Field xApprovedBy Sponsor Managing System Migration and Archiving 8-67 To add content ID prefixes: 1. Set up the following value map on the first Oracle Content Server instances import archive: 2. Set up the following value map on the second Oracle Content Server instances import archive:

8.8.7.5 Changing Release Dates

In this example, you are copying archives to other Oracle Content Server instances using replication or transfer, but you want the release date on the target Oracle Content Server instance to be the date the content item was copied. 1. Set up an export and import for replication or transfer. 2. Select the archive to import in the target Oracle Content Server instance. 3. Set up the following import value map for the archive: The release dates will reflect the local date and time of the target Oracle Content Server instance.

8.8.8 Configuration Migration Tips

There are several points to keep in mind when using the Configuration Migration Utility. ■ If you use directory locations on the target system that differ from the standard Oracle Content Server installation directories, you cannot use Configuration Migration but must do a manual copy of the pertinent directories. For example, if you use partitioned file systems and want to split Oracle Content Server storage on the partitions, you must add configuration variables to the DomainHomeucmcsbinintradoc.cfg file to point to the correct locations for the directories that are stored elsewhere. ■ If you are using different web servers for the source and the target systems, make sure to exclude the web server information when using Configuration Migration to prepare an export. ■ Not all components can be exported using the Configuration Migration Utility. For example, components that require an interactive installation cannot be exported. They must be installed separately on the target system. ■ Dynamic Converter rules are not transferred with the Configuration Migration Utility. They must be manually added to the target system by copying the dataconversioncvtemplates.hda file from the source system to the target system. Input Value Field Output Value All checkbox Content ID server2_dDocName Input Value Field Output Value All checkbox Content ID server1_dDocName Input Value Field Output Value All checkbox Release Date dateCurrent