Migrating Document Libraries

If your company upgrades Library Central from a release prior to V6R2013, you must migrate your data from the previous structure to the current structure.

In V6R2013, the Document Library structure is enhanced to use the same classification capabilities as general and part libraries. Bookshelves and books have been replaced with Document Families. You can create a structure of Document Families and Sub Document Families as simple or complex as required to support your business processes.

See Migration of the Document Library Structure for details about how the schema is migrated, and the files generated by the migration.

Before you begin: Upgrade the Library Central V6R2013 software and all its prerequisites, especially ENOVIA Business Process Services.

  1. Open an MQL window and execute these commands: 

    set context user creator;
 execute program emxLibraryCentalDocumentSchemaMigrationFindObjects <NUM> <IDSFILEPATH>;

    where:


    • <NUM> is the number of IDs to write in each file (default is 100)
    • <IDSFILEPATH> is the directory where the temporary files should be written

    For example:

    execute program emxLibraryCentalDocumentSchemaMigrationFindObjects  100 'C:/Temp/ids/';

    This command generates flat files that contain object IDs for all Document Library objects, all Bookshelf objects that are not connected to a Document Library, and all Book objects not connected to any Bookshelf. The commands writes 100 (or whatever <NUM> value is specified) IDs per file in the indicated folder and names the files objectids_n.txt, where n is consecutive integers.

  2. Execute this MQL command: 

    execute program emxLibraryCentalDocumentSchemaMigration <IDSFILEPATH> <START> <END> <DEBUG>;

    where:


    • <IDSFILEPATH> is the directory where the object ID file were written (see step 1)
    • <START> is the minimum range, where 1 is the file objectids_1.txt.
    • <END> is the maximum range, and n indicates all files starting from the minimum range value
    • <debug> is an optional parameter that logs debug information in the migration log.

    For example:

    execute program emxLibraryCentalDocumentSchemaMigration 'C:/Temp/ids/' 1 n;

    This command creates the new Document Library structure, with Bookshelf and Book objects converted to Document Family objects, and all Generic Documents added to a Document Family object that replaced a Book object.

    Changes are committed to the database when a file is completed without any errors. If an error occurs within a file, ALL object IDs in that file are not migrated, and the migration process continues with the next file. You can rerun the command in step 2 starting with that file as the <START> and <END> values. See the unConvertedObjectIds_xx.csv file for details about any errors (see Log Files for information about this file).

The script adds a property LibraryCentralDocumentSchemaMigrationR213 to the eServiceSystemInformation.tcl program object. When all files exported in Step 1 have been successfully migrated using Step 2, the script sets the value of this property to PostMigrationComplete.