Steps for migration content with a folder from one oracle Content Server to another Content Server

WZh, June, 2013Step 1. Basic Information

Step 2. Prerequisites Setup at source and target Content Server for Migration

Step 3. Create an Archive at Source Content Server- ONE for Export

Step 4. Create an Archive at Target Content Server- TWO for Import and mark it Targetable

Step 5. Create outgoing provider at the target Content Server- TWO

Step 6. From Target Server, setting a Transfer Destination for source archive

Step 7. Doing an export from source CS- ONE

Step 8. Initiating a Manual Transfer from ONE to TWO

Step 9. First Time Import content folder at target CS – TWO

Step 10. Daily Content Update from Source CS to target CS


Step 1.       Basic Information

 

All these information is the server ONE and TWO case, you need to get these information for servers. If you are going to have many CS, each archive should have a unique name to tell it is export to which server or import from which server. Because for transfer to work, archive will have a one to one link relation in future, each source archive only point to one destination target archive.

Source CS                                          http://server1one:16200/cs

Source CS instance name:             server1one16200

Source archive name:                     ExportToTWO

Source Contribution Folder ID:  11111111111111111

 

Target CS                                           http://server2two:16200/cs

Target CS instance name:              server2two16200

Target archive name:                     ReceiveFromONE

Target Contribution Folder ID:  222222222222222222

 

Step 2.       Prerequisites Setup at source and target Content Server for Migration

 

1.      I suppose you have two Content Server (CS), one is source CS, one is target CS. Major version should be same. I suppose your CS not using the “Automatically assign a content ID on check-in” too, this is default setting for CS.
In this example, we migrate from a ONE server to a TWO server. For the Prerequisites steps, you need to do these configurations on both UCM.

2.      To prepare, for webcenter application, we should have the WebCenterConfigure  enabled. For the folder and content export/import, you must have the FoldersStructureArchive component enabled on both the source and target Content Sever instances.
Login to your CS with admin account and enable this component. Go to Administration -> Admin Server ->“Component Manager” under the admin feature. Click “advanced component manager”.
Enable the WebCenterConfigure and FoldersStructureArchive.

Then you need to restart your CS to enable the component. At TWO server, you can start stop UCM from the EM like this:

3.      On both CS, setup the flag for FoldersStructureArchive:
Login to CS , and go to Go to Administration -> Admin Server -> “General Configuration” under the admin feature, we need to set up some flags for CS:

ArchiveFolderStructureOnly

By default is false, no need change as we want include content

AllowArchiveNoneFolderItem

is set to true by default, we need to set to false as we only need our selected folders will get exported into the archive.

AllowArchiveNoneFolderItem=false

ArchiveFolderStructureOnly=false

Click “Save” button.

You also need to restart the CS server.

4.      You will also need to make sure the custom metadata fields on both instances are identical. If they are mismatched, the folders will not import into the target instance correctly. You can use the Configuration Migration Utility to migrate those metadata fields.  NO need this step s we do not have custom meta at this stage.

5.      Now your prepare steps are ready!

Step 3.       Create an Archive at Source Content Server- ONE for Export

 

1.      At the source CS – ONE, once the component is enabled and configurations set, go to Administration -> Admin Applets -> Archiver.

2.      And select Edit -> Add, to create a new archive,

Name as “ExportToTWO

3.      Now that archive is established, let us create a collection to use this archiver.
Go back to the browser and go to Administration -> “Folder Archiver Configuration.
Then select your Archive Name from the list: “ExportToTWO”.
Expand the folder hierarchy and you can now select the specific folder(s) you want to migrate. For our, we select the “test” folder to check it.
Once they are selected, click the Add (or Update) button to save the configuration.

4.      This will add the right criteria to the archive to know what folder will be exported.

Step 4.       Create an Archive at Target Content Server- TWO for Import and mark it Targetable

1.      At the target CS TWO, go to Administration -> Admin Applets -> Archiver.

select Edit -> Add, to create a new archive,

2.      Name as “ReceiveFromONE”

3.      Click OK, we just done the archive create on target server TWO. let us mark it targetable, so transfer can transfer batch to it.

4.      High light to Select the target archive in TWO:
Example – “ReceiveFromONE”

5.      Select “Transfer to” tab and Click “Edit” in the Transfer Options section.

6.      Select “Is Targetable”. Click OK.

Step 5.       Create outgoing provider at the target Content Server- TWO

 

1.      As we will use pull transfer, we will create an outgoing provider at the target server to link to the source CS.  After this is done, from the target TWO, we can open the archive collections at the source – ONE.

2.      So that TWO CS is the target for us. http://server2two:16200/cs

Go to “Administration” àProviders

3.      Click “Add” to add an outgoing provider:

4.      Then input info like this:

Field

Description Our case example
Provider Name Enter a name. This will become a subdirectory in the DomainHome/ucm/cs/data/providers/ directory. ONE_Provider
Provider Description Enter a user-friendly description. For example, Transfer Provider. transfer files from ONE
Server Host Name Enter the server host name of the target Content Server instance. For example, extranet_server. server1one
Server Port Enter a unique port number on which the provider will communicate with the target Content Server instance. 4444
Instance Name Enter the name of the target Content Server instance. For example, instance_on_extranet. server1one16200
Relative Web Root Enter the relative web root of the target Content Server instance. For example, /company/. /cs/

Click the “Add” button to create this provider.
If you configure the QA or production, these info will have difference, you need to get it by yourself.

5.      You need to restart your CS to make the provider can work.

6.      After restart, at the TWO CS, you can use test button to test connection works or not.

You will be able to open the ONE’s archives from TWO.

Step 6.       From Target Server, setting a Transfer Destination for source archive

To specify the target archive to receive transferred content:

1.      Open Archiver from the Content Server instance that will own the transfer. For our case. You will use a pull transfer; the transfer owner is the target Content Server instance. – TWO

2.      At the TWO server, open the remote archive collection that contains the source archive. From Options, choose Open Archive Collection.

3.      Select the collection from the list, we need to browse to a new collection as follows (as this is first time.)

a.      To select the collection from a remote Content Server instance(ONE):

Click “Browse Proxied”

b.      The Browse for Proxied Collection Screen is displayed. The list includes all Content Server instances to which an outgoing provider has been set up.

c.      Select the Content Server instance in the Proxied Servers list. – server1one16200

d.      Select the collection in the Collections list.
server1one16200

e.      Click OK.

Now we get the collection at ONE, select it and Click Open.

4.      You open the collections of ONE now, Select the source archive (server1one16200 — ExportToTWO) in the Current Archives list.

5.      Click the “Transfer to” tab for the archiver of “ExportToTWO”,  and then Click Edit in the “Transfer Destination” section.

6.      The Archive Collections Screen is displayed. Select the collection that contains the target archive. As our target CS is the TWO, so you should select server2two16200 – then select target archive ReceiveFromONE
Click OK.

7.      Now you should have made the server1one16200 – ExportToTWO to point its target destination to server2two16200 –ReceiveFromONE

 

Step 7.       Doing an export from source CS- ONE

1.      Up to now, we have done, create archive at both source and target CS, set the target archive targetable, create provider to link the source and target CS, set the source archive destination to point to target archive. Now we can start export at source CS.

2.      Log to source CS – ONE

3.      Go to the Archiver applet: Administration -> Admin Applets -> Archiver.  Highlight the archive and right click to select Actions -> Export.

4.      Be sure ‘Export Tables’ is selected.

5.      After you click ok to start the export, Now you see the, bottom of the applet showing the exporting status ongoing:

6.      Wait it done and you get the export archive files now.

7.      Once completed, you can click on the “View Batch Files” button to verify the results.  If you highlight the Collections row and click Edit, you can view and verify the results.

Step 8.       Initiating a Manual Transfer from ONE to TWO

To transfer content manually:

1.      Log to target CS – TWO

2.      Go to the Archiver applet: Administration -> Admin Applets -> Archiver

3.      At the TWO CS, open the Archiver on the source Content Server instance – ONE. (Steps is abit same with 7.2-7.3):
“Open Archive collection” of ONE-d001 that contains the source archive.:

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

5.      High light the source archive: ExportToTWO, right click to Select Actions, and then click Transfer.

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

Step 9.       First Time Import content folder at target CS – TWO

1.      Next step is to make a map between two CS. As our folder’s parent folder has different ID in deferent CS, so we need to set a map for parent folder ID when doing import. Let us get two parent folder ID first:

a.      Go to Source CS and Target CS , write down the parent folder ID, for our case is “Contribution Folders

b.      Move your mouse to the “Contribution Folders” at the Source CS ONE, you can get a link like this:  http://server1one:16200/cs/idcplg?IdcService=COLLECTION_DISPLAY&hasCollectionID=true&dCollectionID=11111111111111111

c.      11111111111111111 is the source parent folder ID.

d.      Use same method to get ID from target server TWO.  Link like this: http://server2two:16200/cs/idcplg?IdcService=COLLECTION_DISPLAY&hasCollectionID=true&dCollectionID=222222222222222222

e.      Source ONE “Contribution Folders” id is – 11111111111111111

f.       Target TWO “Contribution Folders” id is – 222222222222222222

2.      Login to target CS – TWO

3.      Go to the Archiver applet: Administration -> Admin Applets -> Archiver

4.     On the target CS –TWO instance and highlight the archive ReceiveFromONE.  Click on the “Import Maps” tab and then on the “Table” tab.  Double-click on the folder and then expand they date entry.  It should then show the Collections table.

If your Collections not found, you cannot do import.

5.     Click on the Edit button for the Value Maps. For the Input Value, you want to enter the value of the dCollectionID of the parent folder from the source instance. In our example, this is 11111111111111111. For the Field, you want to change this to be the dParentCollectionID. And for the Output Value, you want this to be the dCollectionID of the parent folder in the target instance.  In our example, this is 222222222222222222.

6.      Click the Add button.  Do not input wrong ID here as later you cannot change it, unless you recreate your import archive. And then click OK.
This will now map the folder “test” into the correct location on target CS.

7.      The archive is now ready to be imported.  Click on Actions -> Import and be sure the ‘Import Tables’”check-box”is checked.

 

8.      Wait for Import finished. Status text is under left bottom of applet window.

9.      To check for any issues, be sure to go to the logs at Administration -> Log Files -> Archiver Logs.
And that’s it. Your folders and files should now be migrated over.

10.   Go to “Browse Content”, you should be able to see the “test” folder and its content moved to TWO server now.


 

Step 10.  Daily Content Update from Source CS to target CS

 

After you first time done the import at target CS, you in fact has built an import ready to rn at target server already, you do not need to setup the Values Map in future.

Every time at source server has one or more content is changed, and you want to sync these updates to the target server only. You just need to:

1.      Make the export by using Step 7, and then you will get a new batch. Click the “View Batch Files” can let you see what batches you have exported.

2.       Then trigger a transfer by Step 8.
At the target CS you will get the batches you exported.

3.      For example, you have added new file called test1.html at source CS, now you want to import it to the target CS. You can select latest batch and click “Edit” button.

4.      You can get a batch details to list each file and each release of this file; find out the test1.html and its releases. You need use page down, page up feature at here.

Select the releases and click import to import single or multiple releases.

5.      After it is done import, you can see content at the CS now.

6.      By this way, you can sync any new or exit files’ releases to target CS! Done.

Reference : 

http://docs.oracle.com/cd/E23943_01/doc.1111/e10792/c08_migration.htm

https://blogs.oracle.com/kyle/entry/migrating_folders_and_content_together

http://hostilecoding.blogspot.com/2013/05/oracle-ucm-manually-transfer-files.html

http://docs.oracle.com/cd/E14571_01/doc.1111/e10792/c06_migration013.htm

http://docs.oracle.com/cd/E14571_01/doc.1111/e10792/c06_migration004.htm

Advertisements