WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Staging a document library to production

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. You 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. In addition, be logged in as the same user on both the staging and production systems.

If it is not possible to set up a directory that is shared between the staging and production servers, you can complete the migration by manually copying the export files from the staging server and moving the files to the production server import directory. Follow these steps to export and transfer a document library to a production system:

  1. Update the portal_server_root/jcr/migration/conf/pdm60_s2p_conf.xml file on the source (staging) system. Confirm that the following properties in the init section are set as specified, modifying the properties if necessary:

    • MigDirSource: The migration directory on the source (staging) server. This directory will be used for export from the staging server. Make sure 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 (production) 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 (production) server. In the case where a shared directory is not possible, and the exported data have been manually copied to the target (production) server, this property is the import directory where the exported data are stored.

    • SourceServerPort: The host name and port for the source (staging) server. By default, the port for the 6.0 portal server is 10038.

    • TargetServerPort: The host name and port for the target (production) server. By default, the port for the 6.0 portal server is 10038.

    • ExportUserId: If the source (staging) administrator is not the default (wpsadmin), set this value to the source (staging) administrator short name.

    • ExportPassword: Change if not the correct value for the source (staging) administrator password.

    • ImportUserId: If the target (production) administrator is not the default (wpsadmin), set this value to the target (production) administrator short name.

    • ImportPassword: Change if not the correct value for the target (production) administrator password.

    • DocLib: The name of the Document Library to transfer.

    • DocLibProperty: Set the value for this property to icm:title .

  2. Optional: 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 portal_server_root/jcr/migration/conf/pdm60_s2p_conf.xml file on the source (staging) 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. On the source (staging) server, make sure you are in the portal_server_root/migration/ directory, then run the WPmigrate command line script with the staging-to-production-pdm60-export migration task.

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

    2. Verify that the export directories were populated correctly.

  5. Import the document library to the production system. On the target (production) server, make sure you are in the portal_server_root/migration/ directory, then run the following: 

    WPmigrate.bat staging-to-production-pdm60-import

    1. Verify that this transfer step completed without errors. If any errors occurred, check the portal logs on the target (production) server for extended diagnostic information.

 

Troubleshooting staging a document library to production

In order for the staging to production process to succeed, Portal users on the source and target must be the same. The process will fail if there are users in the staging system that are not there in the production system, for example. The two environments, staging system and production system, need to be the same, including the Portal users.

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