IBM FileNet P8, Version 5.2.1            

Starting Bulk Import Tool

You can start Bulk Import Tool from the command line.

Before you begin

Before you run Bulk Import Tool, you must have a working folder that contains the transact.dat file. For example, working folder/eob/transact.dat. The transact.dat file contains the information for each document in the batch.

You must use the Java Runtime Environment (JRE) that is installed with Content Engine Client. Using a different JRE results in errors when documents are imported.

Procedure

To start Bulk Import Tool:

Enter the following command from the command line: Start of change
"Content_Platform_Engine_Client_installation_JRE_path\java" -classpath 
Content_Platform_Engine_Client_installation_path\lib\Jace.jar
Bulk_Import_Tool_installation_path\BulkImport.jar
bulkImport.BI_Start
End of change

Where:

Start of changeContent_Platform_Engine_Client_installation_JRE_pathEnd of change
Start of changeis the path to the folder where the Content Engine Client JRE is installed, for example, "C:\Program Files (x86)\IBM\FileNet\ContentEngine\tools\_jvm17\jre\bin".End of change
Content_Platform_Engine_Client_installation_path
is the path to the folder where Content Engine Client is installed.
Bulk_Import_Tool_installation_path
is the path to the folder where the BulkImport.jar file is located.

Examples:

Windows
"C:\Program Files (x86)\IBM\FileNet\ContentEngine\tools\_jvm17\jre\bin\java" -classpath
"C:\Program Files (x86)\IBM\FileNet\CEClient\lib\jace.jar;
C:\Program Files (x86)\IBM\FileNet\ContentEngine\tools\CEBI\BulkImport.jar"
bulkImport.BI_Start
Start of changeUNIXEnd of change
/opt/IBM/FileNet/ContentEngine/tools/_jvm/jre/bin/java -classpath
/opt/IBM/FileNet/CEClient/lib/Jace.jar
:/opt/IBM/FileNet/ContentEngine/tools/CEBI/bulkimport.jar
bulkImport.BI_Start
Start of changeWindows with a Content Platform Engine Web Services transport End of change
Important: When you use Content Platform Engine Web Services (CEWS) transport to call Bulk Import Tool, you must add three extra JAR files to the class path (stax-api.jar, xlxpScanner.jar and xlxpScannerUtils.jar).
"C:\Program Files (x86)\IBM\FileNet\ContentEngine\tools\_jvm17\jre\bin\java" -classpath
"C:\Program Files (x86)\IBM\FileNet\CEClient\lib\jace.jar;C:\Program Files
 (x86)\IBM\FileNet\CEClient\lib\stax-api.jar;C:\Program Files
 (x86)\IBM\FileNet\CEClient\lib\xlxpScanner.jar;C:\Program Files
 (x86)\IBM\FileNet\CEClient\lib\xlxpScannerUtils.jar;C:\Program Files
 (x86)\IBM\FileNet\ContentEngine\tools\CEBI\BulkImport.jar"
bulkImport.BI_Start
Start of changeUNIX with a Content Platform Engine Web Services transportEnd of change
Important: When you use Content Platform Engine Web Services (CEWS) transport to call Bulk Import Tool, you must add three extra JAR files to the class path (stax-api.jar, xlxpScanner.jar and xlxpScannerUtils.jar).
/opt/IBM/FileNet/ContentEngine/tools/_jvm/jre/bin/java -classpath
/opt/IBM/FileNet/CEClient/lib/Jace.jar
:/opt/IBM/FileNet/CEClient/lib/stax-api.jar
:/opt/IBM/FileNet/CEClient/lib/xlxpScanner.jar
:/opt/IBM/FileNet/CEClient/lib/xlxpScannerUtils.jar|
:/opt/IBM/FileNet/ContentEngine/tools/CEBI/bulkimport.jar
bulkImport.BI_Start


Last updated: October 2015
p8pit026.htm

© Copyright IBM Corporation 2015.