Many of the components that make up IBM®
FileNet® Content Federation Services for Content
Integrator can generate log files
that you can use to help troubleshoot problems that occur during installation,
configuration, or normal use.
Installation log files
IBM
FileNet Content Federation Services for Content
Integrator generates logging output that is related to
installation. The name and location of the log file is
cfs_install_root/federator_install_log_/data/<version>.txt/.
Exporter log files
The content federation exporter generates logging output that is related to the export phases of
content federation, which includes querying the source repository for documents that satisfy the
criteria that are specified by federation rules and building export requests for each document
found. The amount of information that is generated and the name of the log file depends on the
configuration settings that are specified by using the Federation Administration application. The
exporter provides for five different logging detail levels, in order of least to most detailed:
FATAL, ERROR, WARN, INFO, and DEBUG. The default logging level is INFO. The location and default
name for log file is
cfs_install_root/FedExporter/logs/federator.log. For more
information about configuring logging for the exporter, see General Configuration
page of the Federation Administration application.
Each exporter log entry is prefixed by the name of the component that generated it:
- Scheduler - Log entries that are generated by the Scheduler contain information on the status of
each rule and also entries that map rule names to Run IDs. An entry for each rule is generated
periodically according to the refresh interval set by using the Federation Administration
application.
- RunDispatcher - Log entries that are generated by the RunDispatcher contain information on how
the rules are dispatched to the run workers. Log entries are also created that indicate the state of
the queue that contains rules that are ready to be dispatched and processed by the run workers.
- RunWorker-<thread number> - Log entries that are generated by RunWorkers contain information
on the processing of the rules. Individual log entries are generated to indicate when processing
starts, the selection criteria that is used, and how many items are selected by the rule for a
particular execution.
- ExportDispatcher - Log entries that are generated by the ExportDispatcher contain information on
how the batches are dispatched to the export workers. Log entries are also created that indicate the
state of the queue that contains batches that are ready to be dispatched and processed by the
export workers.
- ExportWorker-<thread number> - Log entries that are generated by ExportWorkers include
information on the processing of the batches of export requests. Individual entries are generated
that indicate how many import requests were generated and how many items were exported successfully
or how many failed during the federation.
Content Integrator log files
IBM Content Integrator generates two logs that can be useful to examine when
you diagnose problems with IBM
FileNet Content Federation Services for Content
Integrator. The first file is the
output that is generated by the RMI proxy server JVM in which the IBM
FileNet Content Federation Services for Content
Integrator connector for your source repository is hosted. Output is
typically written to stdout and must be redirected to a file, but can also be configured to write to
a logging server that runs as part of IBM Content Integrator
VeniceBridgeServices. For more information about configuring trace logging for the RMI proxy
connector, see the IBM Content Integrator online documentation.
The second log file is generated by Venice Bridge Services and contains log entries that are
generated by the following IBM Content Integrator services that are used by
content federation: Configuration Server, the Session Pool Server, and the SSO Server. The name and
location of the file that contains the log is
cfsici_install_root/VeniceBridge.log.
To enable IBM Content Integrator debug logging, see Configuring client application logging.
Importer log files
Log messages that are related to the import phase of federation are generated by the
Content Platform Engine server and are written to an error log or a trace log
depending on the nature of the message. The default location for both files is a subdirectory that
is called
FileNet/server_instance_name under the current working directory of
the deployed application. The default name for the error log file is
p8_server_error.log and the trace file default is
p8_server_trace.log.
- For WebSphere® application servers,
the default log file location is typically in a directory named
WAS_INSTALL_ROOT/profiles/PROFILE_NAME/FileNet/SERVER_INSTANCE_NAME
- For Oracle WebLogic servers, the default log file location is typically in a
directory named
INSTALL_ROOT/user_projects/domains/DOMAIN_NAME/FileNet/SERVER_NAME/
- For JBoss servers, the default log file location is typically in a directory
named
JBOSS_INSTALL_ROOT/jboss-as/bin/FileNet/SERVER_INSTANCE_NAME/
For more information of about enabling and configuring trace logging for the
Content Platform Engine server, see
Trace
logging.
Federation Administration application log files
Messages that are generated by the Federation Administration application are logged to the
application server log files where the application is deployed. For cluster environments, provide
the log files from each server. Each server stores log files as follows:
- WebSphere - all files in the following directories: install_root/profiles/profile_name/logs/server_name,
install_root/profiles/profile_name/logs/ffdc
- WebLogic:
install_root/user_projects/domains/domain-name/servers/server-name/logs
- JBoss:
install_root/server/server-name/log