Content Manager 25.2 DataPort Help

# Origins and BulkLoader

## Origins

As Content Manager DataPort uses the BulkLoader for some of the import processes, an Origin is created for each Import Project. An Origin is created in the Content Manager database that the objects are imported into. The Origin created with the same name as the project.

If the Import Project is executed multiple times, the same Origin object will be used and a new Origin history will be created. Each execution of an import using an Origin is known as an Origin Run.

Origins can be used to find the objects that were created when processing a Content Manager DataPort project. To find the created objects:

1. In Content Manager, from the Manage menu, click Origins.
2. Right-click on the Origin name and click Show History.
3. From the displayed Origin Histories, select the history whose items you want to find, right-click and click Show Records.

   The Records that were created with that Origin History Run will be displayed in a Content Manager window.

For further information about Origins and working with Origins see Content Manager Help > Origins.

## BulkLoader

Importing using the BulkLoader

The use of the BulkLoader option in Content Manager Dataport requires that the customer is confident that the data for bulk loading has been sanitized correctly prior to import. All integrity checks should be applied before executing the bulk loading process. If there are any doubts about the validity of the data to be loaded then the BulkLoader feature should be disabled so that all inbuilt Content Manager integrity checks are applied.

The BulkLoader option is specifically included to optimize the speed of importing data. As a general rule, we bypass any code that would results in a round trip to the database. This would include bypassing checks for duplicate records.

The primary goal is speed, so no assumptions about data integrity should be made, beyond the fact that the input is appropriate for the SQL tables to which the data is targeted.

Importing Locations

As a single Origin object may be used for both Records and Locations, an Origin must have a default Record Type. When importing Locations using the BulkLoader with Content Manager DataPort, a Record Type named DataPort Default is created and used for this purpose. For further information, see Importing Locations.

Copyright 2008-2025 Open Text
Version 25.2 | Last updated July 2023
Contact

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to hprmdocumentation@microfocus.com.

We appreciate your feedback!

Product: Content Manager 25.2

Topic Title: Origins and BulkLoader