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.
Procedure
To enable Bulk Import Tool client logging:
- In the directory where the tool is started, create a file
that is named log4j.properties.
- Open the file and add the following lines:
log4j.rootLogger=ERROR, TXT
# log4j.logger.com.filenet.wcm.api.impl.RemoteCommand=WARN
# log4j.logger.com.filenet.wcm.api.impl.RemoteCommand=DEBUG
log4j.appender.TXT=org.apache.log4j.FileAppender
log4j.appender.TXT.layout=org.apache.log4j.PatternLayout
log4j.appender.TXT.layout.ConversionPattern=%-4r %d [%t] %-5p %c{1} %x - %m%n
log4j.appender.TXT.File=c:\\cebiClientLog.txt
log4j.appender.TXT.Append=false
log4j.logger.filenet_tracing = off
log4j.logger.filenet_tracing.api.detail.moderate.summary = debug
log4j.logger.filenet_tracing.api.detail.moderate = debug
log4j.logger.filenet_tracing.api.detail = debug
- Modify the log4j.appender.TXT.File= entry
in the properties file so that it uses a valid path and file name.
Modifying the entry specifies the location and name of the output
log file.
- 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: -Dlog4j.configuration=file:log4j.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:
"C:\Program
Files (x86)\IBM\FileNet\ContentEngine\tools\_jvm17\jre\bin\java" -Dlog4j.configuration=file:log4j.properties
-classpath "C:\Program Files (x86)\IBM\FileNet\ContentEngine\lib\Jace.jar;C:\Program
Files (x86)\IBM\FileNet\ContentEngine\lib\log4j.jar;C:\Program Files
(x86)\IBM\FileNet\ContentEngine\tools\CEBI\bulkimport.jar" bulkImport.BI_Start
-h C:\CB521\config1