IM Relationship Resolution Information Center, Version 4.2

Configuring custom pipeline logging

IBM Relationship Resolution provides default pipeline logging configurations that determine how pipelines log errors and messages in both debug mode and service/daemon mode. But you may want to modify the default pipeline logging configuration or create a custom logging configuration to meet your organization's needs. To do so, you must create two logging files that specify the custom logging configuration and then modify the pipeline configuration file to use those custom logging files.

About this task:
Pipeline logging is by pipeline node, so you will need to make these changes on each pipeline node. After you create them, you can copy the debug and standard configuration files to each pipeline node. You can also either copy-and-paste the text from the [logging] section from one pipeline configuration file to another, or you can copy the entire pipeline configuration file from one pipeline node to another. Just remember to adjust the connection settings, as appropriate.
Procedure:
  1. Using any text editor, create two files:
    1. A debug configuration file, used to specify the logging for pipelines operating in debug mode
    2. A standard configuration file, used to specify the logging for pipelines operating in service/daemon mode
  2. In each file, use the appropriate pipeline logging components to instruct the system how to log in that mode.
  3. Save each file. It is a good idea to save these files to the same directory where the pipeline configuration file is located.
  4. In the pipeline configuration file, add a new section named [logging]. This is the section where you will specify the names of the two logging configuration files that you created.
  5. Under the [logging] section heading, add the following two settings:
    1. DebugConfigFile=debug logging configuration filename
    2. ConfigFile=service/daemon logging configuration filename
      Note: If you saved the logging configuration files in a directory other than the directory where the pipeline configuration file is located, be sure to indicate the full path to the file.
  6. Save the changes to the pipeline configuration file.
What to do next:
Before these logging changes take effect, you will need to stop and restart all running pipelines on each affected pipeline node.


Feedback

Last updated: 2009