Skip Headers
Oracle® Student Learning Installation and Deployment Guide
Release 3.1.3

Part Number E20664-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

13 Migrating Content from UCM 10g to ECM 11g

Follow these steps to migrate content from UCM 10g to ECM 11g.

  1. Complete ECM 11g installation and verify that you can check in content. Complete the OSL setup using the deployment instructions.

  2. Export schema from 10g ECM DB. In 10g, the unique IDs are stored in tables (COUNTERS). DocID, RevID, and RevClassID are Unique IDs.

    The main tables that are needed are:

    • DOCMETA

    • DOCMETADEFINITION

    • DOCUMENTHISTORY

    • DOCUMENTS

    • REVISIONS

  3. Import schema to 11g ECM DB. Before importing data from 10g, create OSL metadata in the database to match the 10g configuration.

    In 11g, the unique IDs for Document and Revisions use the database sequence though the table COUNTERS is still available.

    After schema import, set the values of the sequences IDCSEQDOCID, IDCSEQREVID, and IDCSEQREVCLASSID to start at a value higher than the imported data.

  4. Create entries for the content in a new table called REVLCASSES based on the DID and DDOCNAME.

  5. The vault and weblayout directories are:

    • ECM 10g:

      <UCM_HOME>/server/vault
      <UCM_HOME>/server/weblayout
      
    • ECM 11g:

      <MiddlewareHome>/user_projects/domains/<OSL_CS_Domain>/ucm/cs/vault
      <MiddlewareHome>/user_projects/domains/<OSL_CS_Domain>/ucm/cs/weblayout
      
  6. The document type used by OSL in ECM 10g is ADACCT. The document type used by OSL in 11g is Application. To avoid renaming any vault and weblayout directories, create a document type ADACCT in 11g.

    The vault and weblayout directories vary based on the document type.

    ECM 10g:

    <UCM_HOME>/ucm/server/vault/adacct/@osl/@user.name1
    ...Additional directories will be available for each user who has published content
    <UCM_HOME>/ucm/server/vault/adacct/@osl/@oslcontent/@main/
    <UCM_HOME>/ucm/server/vault/adacct/@osl/@oslcontent/@temp/
    <UCM_HOME>/ucm/server/weblayout/groups/osldocuments/@osl/@user.name1/documents/adacct
    <UCM_HOME>/ucm/server/weblayout/groups/osldocuments/@osl/@oslcontent/@main/documents/adacct
    <UCM_HOME>/ucm/server/weblayout/groups/osldocuments/@osl/@oslcontent/@temp/documents/adacct
    

    ECM 11g:

    <MiddlewareHome>/user_projects/domains/<OSL_CS_Domain>/ucm/server/vault/application/@osl/@user.name1
    ...Additional directories will be created for each user who has published content
     
    <MiddlewareHome>/user_projects/domains/<OSL_CS_Domain>/ucm/server/vault/application/@osl/@oslcontent/@main
     
    <MiddlewareHome>/user_projects/domains/<OSL_CS_Domain>/ucm/server/vault/application/@osl/@oslcontent/@temp
    
    <MiddlewareHome>/user_projects/domains/base_domain/ucm/cs/weblayout/groups/osldocuments/@osl/@user.name1/documents/application
    
    <MiddlewareHome>/user_projects/domains/base_domain/ucm/cs/weblayout/groups/osldocuments/@osl/@oslcontent/@main
    
    <MiddlewareHome>/user_projects/domains/base_domain/ucm/cs/weblayout/groups/osldocuments/@osl/@oslcontent/@temp
    

    In addition, the directory structure varies based on different security groups.

  7. Create the directory structure in ECM 11g vault and copy the files from individual folders to these from ECM 10g.

  8. Create the directory structure in ECM 11g weblayout and copy the files from individual folders to these from ECM 10g.

  9. Start the ECM component Repository Manager. Click the Indexer tab and start the Collection rebuild cycle.

  10. On completion of indexing, restart the server.

  11. Log in and click Search. All the migrated content is displayed.

  12. Check in new content and search for the content. The file must be checked in and you must be able to view the content. Click Web Location and Native URL to view the file.

  13. Review the files checked in to confirm that migration is successful.