Stage a document library to production

 

+
Search Tips   |   Advanced Search

 

Overview

Export and transfer a document library from a staging system to a production system.

When a document library is transferred from a staging system to a production system, private drafts are transferred without modification, but submitted drafts are converted to private drafts.

We cannot transfer document versions when staging a document library to production.

Use the following steps to export and transfer a document library from a staging system to a production system.

Before you begin, create an empty shared directory to hold the exported document library. Both the staging system and the production system must have write access to this directory.

 

Procedure

To export and transfer a document library to a production system:

  1. Update the file...

    portal_server_root/jcr/migration/conf/pdm60_s2p_conf.xml

    ...on the source (staging) system. Confirm that the following properties in the init section are set as specified...

    MigDirSource The migration directory on the source server.

    This directory will be used for export from the staging server.

    Verify that this directory is empty and can be shared with the production server.

    MigDirTarget The shared directory on the target (production) server.

    This directory will be used for import to the target server.

    Either the target server maps to the source directory, or the exported data must be copied to the target server's local directory.

    If the source directory is shared, this property is the source directory as it appears on the target server.

    If the exported data are copied to the target server, this property is the local directory where exported data are stored.

    SourceServerPort The host name and port for the source server.

    By default, the port for the 6.0 portal server is 10038.

    TargetServerPort The host name and port for the target server.

    By default, the port for the 6.0 portal server is 10038.

    ExportUserId If the source administrator is not the default (wpsadmin), set this value to the source administrator short name.
    ExportPassword Change if not the correct value for the source administrator password.
    ImportUserId If the target administrator is not the default (wpsadmin), set this value to the target administrator short name.
    ImportPassword Change if not the correct value for the target administrator password.
    DocLib Name of the Document Library to transfer.
    DocLibProperty Set to icm:title.

  2. If there is more than one document library with the same name, export the Document Libraries by UUID. Make the following changes to export Document Libraries by UUID:

    1. Find and record the UUID for the document library that you are transferring. The UUID is accessible through the Manage Document Libraries portlet under Portal Administration.

    2. Update the following properties in the init section of the file...

      portal_server_root/jcr/migration/conf/pdm60_s2p_conf.xml

      ...on the source system:

      DocLib The UUID of the Document Library to transfer.
      DocLibProperty Set the value for this property to jcr:uuid.

  3. Start both the staging and production servers.

  4. Export the document library from the staging system.

    • Log on to the source server

    • cd to...

      portal_server_root/migration/

    • Run

      WPmigrate.[sh|bat] staging-to-production-pdm60-export

      Verify that this transfer step completed without errors. If any errors occurred, check the portal logs on the source server for extended diagnostic information.

      Verify that the export directories were populated correctly.

    • Import the document library to the production system...

      WPmigrate.[bat|sh] staging-to-production-pdm60-import
    • If any errors occur, check the portal logs on the target server for extended diagnostic information.

 

Troubleshoot staging a document library to production

If documents are staged twice using the same staging-production server pair, and the documents have been moved or deleted between the two stagings, then manually delete these documents from the production server before transferring the documents again. If this is not done, an error similar to this example is generated:

javax.jcr.ItemExistsException: A node already exists with uuid: 376dba00408608aea231b2c714d0bda6 at path: /contentRoot/icm:libraries[10]/F1/F3/test1.ort

 

Parent topic:

Staging to production