IBM FileNet P8, Version 5.2.1            

Preparing to use Bulk Import Tool

Ensure that you are properly set up to begin working with Bulk Import Tool.

Before you begin

To work with Bulk Import Tool, you must be knowledgeable about the UNIX or Windows operating system and the Content Platform Engine server.

Before you install and run Bulk Import Tool, ensure that you exclude any Bulk Import Tool directories, such as the home, working, and journal directories, from anti-virus scanning.

About this task

Important: You cannot use Bulk Import Tool to import documents to classes that contain choice lists, binary properties, or multi-valued properties.
The location of the documents to be imported is specified in the transact.dat file. The documents can be in the same directory as the transact.dat file, in a subdirectory, or in a different location. The location of the transact.dat file is specified in the batchname.eob file. The batchname.eob file is in the working directory. The transact.dat file is a text file that contains one row, or line, of information that describes each document within a batch. The transact.dat file tells Bulk Import Tool how to process the batches of documents. The file contains the following information:
  • Information that describes the makeup of each document.
  • A class code to associate the document with a document class, property values to assign to the document, and content description paths, such as the location of the document content.
The syntax for the transact.dat file is as follows:
class_code:document_properties:external_index:files|+file_name
where:
class_code
Is one of the codes that is specified in the CEBI.cfg file for a document class that is involved in the import.
Start of changedocument_propertiesEnd of change
Start of changeIncludes values for each of the properties that are specified in the IndexNames parameter in the CEBI.cfg file. The values must be listed in the same order that they are listed in the DocClassAttribute parameter in the CEBI.cfg file. If a property is set to Required on the Content Platform Engine server, the Bulk Import Tool fails a batch if that property is not set in the transact.dat file. Spaces are considered valid characters, so a required property that contains only spaces can be processed by Bulk Import Tool. Additionally, if there are other characters in the field, the leading and trailing spaces are not removed before they are processed by Bulk Import Tool. Setting a space or non-integer in a property field of an integer returns the error message Value = Bad number conversion and causes the batch to fail.End of change
external_index
Is a value that is recorded in the report when the batch is completed. This value is not imported as part of the document.
files
Specifies one or more names of the content element files that are associated with the document.
file_name
Is the name of a text file that contains a list of the content element file names that are associated with the document.
A simple entry in the transact.dat file looks like the following example. The document uses one image, named cat_picture.jpg, as its content element.
03:67890,"Hi there",3320.09:This is a test:cat_picture.jpg
An entry that lists multiple content element file names looks like the following example. The document uses two images, named kids.tif and ocean_surf.jpg, as its content elements.
03:67890,"Hi there",3320.09:This is a test:kids.tif,ocean_surf.jpg
Alternatively, an entry that specifies a text file that lists the content element file names looks like the following example. The text file x.txt specifies two images, named kids.tif and ocean_surf.jpg, as its content elements.
03:67890,"Hi there",3320.09:This is a test:+x.txt
The actual entries in the x.txt file are as follows:
kids.tif
ocean_surf.jpg


Last updated: October 2015
p8pit006.htm

© Copyright IBM Corporation 2015.