You are here

SkyVault 2.0 » Administering » Using the Bulk Import tool

Importing with the Bulk Import tool

You can bulk import by using the user interface, or with a program.

SkyVault web scripts are used for bulk importing. If you choose to code the bulk import, code examples are provided to help you. In both cases, you can use the reference table to determine the fields and data that are required for a successful import.

If you need to troubleshoot or diagnose any issues with a bulk import, you can enable logging. To enable debugging for the Bulk Import tool, add the following command to the log4j.properties file before deployment: 
log4j.logger.org.alfresco.repo.bulkimport=DEBUG
Set the debug statements to at least INFO level: 
log4j.logger.org.alfresco.repo.batch.BatchProcessor=info
You can also enable logging for the transaction handler to identify any transactional issues during the import: 
log4j.logger.org.alfresco.repo.transaction.RetryingTransactionHelper=info

For more information about log4j, see Log4j.properties file.

  • Bulk importing using the user interface The two types of bulk import (streaming and in-place) each have a user interface, which are implemented using SkyVault web scripts.
  • Bulk importing using a program Code examples show you how to complete a streaming bulk import and an in-place bulk import programmatically.
  • Bulk Import tool fields and values The Bulk Import tool has a number of entry and display fields that are displayed in the user interface, but also referenced in the status.xml file that is used if you are programming a bulk import. The labels, fields, possible values and a summary of each entry is explained in this information.
Parent topic: Using the Bulk Import tool

© 2017 TBS-LLC. All Rights Reserved.