Configuring Oracle WebCenter Interaction Development Kit (IDK) Logging

To enable and configure Oracle WebCenter Interaction Development Kit (IDK) logging, first determine how the IDK is deployed.

Oracle WebCenter Interaction Development Kit (IDK) logging is disabled by default. If logging is enabled, it is sent only to the local machine by default, requiring direct access to the machine to view the logs. These default settings were chosen to secure potentially sensitive information present in log messages.

If the Oracle WebCenter Interaction Development Kit (IDK) is deployed as a web application to support Integration Service implementations, edit the distributed web application configuration file (web.xml or Web.config). For details, see Configuring Java Oracle WebCenter Interaction Development Kit (IDK) Logging (web.xml) or Configuring .NET Oracle WebCenter Interaction Development Kit (IDK) Logging (Web.config)
If the Oracle WebCenter Interaction Development Kit (IDK) is deployed as a library supporting a web application (for example, a portlet), copy and paste the configuration parameters from the IDK's distributed web.xml/Web.config into your web application configuration file. For details, see Configuring Java Oracle WebCenter Interaction Development Kit (IDK) Logging (web.xml) or Configuring .NET Oracle WebCenter Interaction Development Kit (IDK) Logging (Web.config).
If the Oracle WebCenter Interaction Development Kit (IDK) is deployed as a stand-alone application outside a web application context, such as report-generating or data loading and dumping applications using the PRC, use programmatic configuration to initialize logging parameters. Programmatic logging configuration can be done at startup, or by using a static initialization call on a façade class that the web application runtime code uses to obtain logging components or logger instances. For details, see About the Oracle WebCenter Interaction Development Kit (IDK) Logging API.

To use the Oracle WebCenter Interaction Development Kit (IDK) Logging API, you must configure the logging receiver to read logs from the IDK. To configure the log receiver, you must know the logging application name. The Oracle WebCenter Interaction Development Kit (IDK) logging application name is configured in the web application configuration file or set via the initialize() method in the Logging API.

Configuring Java Oracle WebCenter Interaction Development Kit (IDK) Logging (web.xml)For web services using the Java Oracle WebCenter Interaction Development Kit (IDK), the web.xml file is the standard way to configure log instrumentation.
Configuring .NET Oracle WebCenter Interaction Development Kit (IDK) Logging (Web.config)If you are running the .NET Oracle WebCenter Interaction Development Kit (IDK) as a web application that hosts web services (that do not use the logging API), the Web.config file is the best way to configure log instrumentation.
Oracle WebCenter Interaction Development Kit (IDK) Logging LevelsThis page summarizes logging levels and their implementation in Oracle WebCenter Interaction Development Kit (IDK) logging.
Oracle WebCenter Interaction Development Kit (IDK) Logging API Web Application VariablesTo enable Oracle WebCenter Interaction Development Kit (IDK) logging, you must enter the application name and change the settings in the web.xml (Java) or Web.config (.NET) file distributed with the Oracle WebCenter Interaction Development Kit (IDK). This page lists the applicable variables.

Parent topic: About Oracle WebCenter Interaction Logging Utilities

Oracle WebCenter Interaction Web Service Development Guide

Configuring Oracle WebCenter Interaction Development Kit (IDK) Logging