If you want more detailed debug logging information than the information that is provided
in the default logging in the journals file, you can enable client-side logging.
Before you begin
Client-side logging employs a mechanism, based on java.util.logging (JUL),
originally defined by Content Platform Engine. This mechanism allows you to set logging that to be
defined either entirely by JVM arguments or by a combination of JVM arguments and a properties file.
Refer to topic API logging for details on how to utilize JUL.
Procedure
To enable Bulk Import Tool client logging:
- In the directory where the tool is started, create a file that is named
FileNetLogging.properties.
- Open the file and add the following lines:
# Optionally specify a default logging level to apply to all CE subsystems
# for which an explicit value is not given
CELogLevel=
# Specify logging level for each subsystem using one of the values described in the API Logging topic.
# Subsystems which generate logging in client APIs
CESubSystem.API=moderate
- Modify the logging levels in the properties file to return the appropriate level of
logging that you want.
- To enable the logging in Bulk Import Tool, modify the startup script and add the
following entry:
-Dcom.filenet.logging.ConfigFile=.\FileNetLogging.properties
Important: Client logging can increase system usage. Enable client logging only for
debugging purposes.
Example
Here is an example of a startup script with the path specified:java -Xms512m
-Xmx2048m -Dcom.filenet.logging.ConfigFile=C:\CEBI\FileNetLogging.properties -classpath
"C:\CEBI\Jace.jar;C:\CEBI\bulkimport.jar" bulkImport.BI_Start -m -h
C:\CEBI\TestFiles\config