Starting Bulk Import Tool

You can start Bulk Import Tool from the command line.

Before you begin

You must have a working folder that contains the transact.dat file. The transact.dat file contains the information for each document in the batch.

A Java™ runtime is not included in the IBM® Content Cortex installation packages. Provide a Java environment to run the Bulk Import Tool. For guidance on which JREs are supported and how to set the required environment variables set so that the Bulk Import Tool uses the appropriate Java version, see the technote Providing a Java Runtime (JRE) for installing and using IBM Content Cortex External link opens a new window or tab .

To use Enterprise JavaBeans (EJB) transport, Bulk Import Tool must be collocated with Content Platform Engine. When you use Enterprise JavaBeans to call Bulk Import Tool, the AppClient directory must contain the ext, lib, and plugins folders for Bulk Import Tool to be able to connect to Content Platform Engine. The WebSphere® Client installation program can install these folders. Or you can create an AppClient directory folder and copy these folders and their contents from the AppServer folder that is created by the WebSphere Application Server installation program into the AppClient folder. You must also update the following CeUri entry in the CEBI.cfg file to support EJB transport:

CeUri="iiop://localhost:2809/FileNet/Engine"CeUri="iiop://localhost:2809/FileNet/Engine"

Important: Bulk Import Tool can crash when there is not enough heap memory to store all the metadata from Content Platform Engine. To prevent this issue, run Bulk Import Tool with a minimum of 512 MB and a max of 1 GB of memory. If the metadata load from the server increases, this memory requirement might also need to increase.

Modify your command line option to update the memory settings:

.../java -Xms512m -Xmx1024m -cp

Procedure

To start Bulk Import Tool:

Enter the following command from the command line:

"JRE_path\java" -classpath 
Content_Platform_Engine_Java_API_installation_path\Jace.jar
Bulk_Import_Tool_installation_path\BulkImport.jar
bulkImport.BI_Start

Where:

JRE_path: is the path to the folder where the JRE is installed, for example, "C:\Program Files\Semeru\jre-17.0.15.6-openj9\bin".
Content_Platform_Engine_Java_API_installation_path: is the path to the folder where Content Platform Engine Java API 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\Semeru\jre-17.0.15.6-openj9\bin\java" -classpath
"C:\cpetools\CEBI\Jace.jar;
C:\cpetools\CEBI\bulkimport.jar"
bulkImport.BI_Start

Windows on WebSphere Application Server with an EJB transport

"<WebSphere path>\AppClient\java\jre\bin\java" -classpath
"C:\cpetools\CEBI\Jace.jar;
C:\cpetools\CEBI\bulkimport.jar"
   -Djava.ext.dirs=<WebSphere path>\AppClient\java\jre\lib\ext;
       <WebSphere path>\AppClient\lib;
       <WebSphere path>\AppClient\plugins
bulkImport.BI_Start <options>

UNIX

/usr/lib/jvm/ibm-semeru-open-17-jre/bin/java -classpath
/opt/IBM/cpetools/CEBI/Jace.jar
:/opt/IBM/cpetools/CEBI/bulkimport.jar
bulkImport.BI_Start

UNIX on WebSphere Application Server with an EJB transport

<WebSphere path>\AppClient\java\jre\bin\java -classpath
/opt/IBM/cpetools/CEBI/Jace.jar
:/opt/IBM/cpetools/CEBI/bulkimport.jar
   -Djava.ext.dirs=<WebSphere path>/AppClient/java/jre/lib/ext;
       <WebSphere path>/AppClient/lib;
       <WebSphere path>/AppClient/plugins
bulkImport.BI_Start <options>