Oracle E-Business Suite Integrated SOA Gateway allows you to configure new log settings at the integration interface level. Click Add Another Row in the Log & Audit Setup Details page. An empty row is added to the end of the current configuration table letting you add a new configuration for a specific interface. This includes specifying log severity information for runtime log or disabling the runtime log by setting its value to 'Off', as well as enabling or disabling the design-time log and the service auditing feature for the selected interface.
Note: Design-time logs capture only SOAP service activities recorded at design time, including Generate, Deploy, Undeploy, Reset, Retire, and Activate services, only if the design-time log is enabled for that interface or service. Without enabling the design-time log, the logs will not be written.
Perform the following tasks to add a new configuration in a new role:
Identify interface name that the logging will be enabled:
Search and select a desired interface name that you want the logging to be enabled. Once the Interface Name field is selected, the associated Internal Name, Product, and Service Status fields are automatically populated.
Note: Logging is configured at the interface or service level. Configuration at the method or operation level is not supported in this release.
The rest of the configuration fields including Design Time Log, Run Time Log Level, and Audit fields are also displayed with default values. You can change them if needed.
Enable design-time log (optional)
Use the design-time logs to troubleshoot any issues or exceptions encountered during service generation and deployment life cycle. By default, the design-time log is turned off initially once the interface name is selected. However, you can enable the feature for the selected interface by selecting 'On' from the drop-down list.
If the design-time log is enabled for the selected interface or service, logs can be written for the design-time actions such as Generate, Deploy, Undeploy, Reset, Retire, and Activate services. Without enabling the design-time log, the logs will not be written.
For example, an interface 'Order Capture' has the design-time log enabled. At design time during service generation and deployment, logs specific to the selected 'Order Capture' interface can be captured through the Integration Repository user interface. The View Log is displayed in the interface detail page for 'Order Capture' allowing you to view log details and error details if occurred during the design-time activities.
Note: If the design-time log is not enabled, and if any errors occurred while performing the design-time activities, then View Error appears instead for that interface. Clicking View Error to access and view only the error and exception details in the Log & Error Details page.
For more information on viewing design-time logs, see Viewing Generate and Deploy Time Logs.
Enable the auditing feature (optional)
By default, the auditing feature is turned off once the interface name is selected. You can enable the feature to create audit trail for the interface by selecting 'On' from the drop-down list.
If the auditing feature for a specific interface or service is enabled, all SOAP messages for the interface or service that Oracle SOA Suite processes along with the associated payloads and fault messages can be saved and audited through Service Monitor.
For more information about Service Monitor, see Monitoring and Managing SOAP Messages Using Service Monitor.
Enable the runtime log by selecting log severity (optional)
By default, the runtime log is turned off once the interface name is selected. You can enable it by changing the log severity level in the Run Time Log field.
Log level is used to control logging output for the enabled service. Select a different value other than the default 'Off' from the drop-down list to enable the runtime log.
At run time during the invocation of Oracle E-Business Suite services by Web service clients, if a service has the runtime log enabled, the associated log messages for SOAP services are captured and can be viewed through Service Monitor. Click the Log icon in the search result table in Service Monitor to open the Web Service Runtime Logs page where you can view logs recorded for the service against a specific instance.
Attention: Runtime logging for PL/SQL, Concurrent Program, XML Gateway interface types is handled by Oracle SOA Suite; therefore, setting runtime log levels for these services in the Log & Audit Setup Details page here will display Oracle SOA Suite logs if the services are deployed in Oracle SOA Suite. Limited runtime log statements from the Oracle E-Business Suite Integrated SOA Gateway code (identified by the package name oracle.apps.fnd.isg) will be displayed for these services.
Runtime logging for Business Service Object interface type is handled by Oracle E-Business Suite Integrated SOA Gateway; therefore, Service Monitor shows Oracle E-Business Suite Integrated SOA Gateway logs for these interfaces based on the log level selected here.
For more information on viewing runtime logs, see Viewing Service Processing Logs.
Log Level
The following table describes the available log levels used for the runtime log:
Log Level
| Severity | Description |
|---|---|
| Off (default) | It is a special level that can be used to turn off logging. |
| Severe | It is a message level indicating a serious failure. |
| Warning | It is a message level indicating a potential problem. |
| Information | It is a message level for informational messages. |
| Configuration | It is a message level for static configuration messages. |
| Fine | It is a message level providing tracing information. |
| Finer | It indicates a fairly detailed tracing message. |
| Finest | It indicates a highly detailed tracing message. |
Please note that log messages can be correlated across middle-tier and database servers. If a new configuration is added for a service that has been deployed, the newly-configured log setting including runtime log level configured for that deployed service will be added in the Oracle SOA Suite. When the configuration is deleted for a deployed service, the runtime log level would be reset at the composite level as well in Oracle SOA Suite. The same mechanism applies when an integration administrator updates an existing log level for a deployed service, the new log level will be updated in the database.
If a new configuration is added for a service that is not deployed, then the runtime log configuration including log level set for that service would be effective after the service is deployed.
To add a new configuration:
Log in to Oracle E-Business Suite as a user who has the Integration Administrator role. Select the Integrated SOA Gateway responsibility.
Select Administration > Configuration from the navigation menu. The Log & Audit Setup Details page is displayed.
To add a new configuration, click Add Another Row.
An empty row appears allowing you to enter the following information:
Interface Name: Specify an appropriate interface name for the log is configured.
Once the Interface Name field is selected, the associated Internal Name, Product, and Service Status fields are automatically populated. The rest of configuration fields such as the Design Time Log, Run Time Log, and Audit fields are also displayed with default values. You can change them if needed.
Design Time Log: By default, it is set to "Off'. You can enable the design-time log by selecting 'On' from the drop-down list.
Run Time Log: By default, it is set to "Off' and the runtime log is turned off. You can change the default value by selecting an appropriate value from the drop-down list.
Audit: By default, it is set to "Off'. You can enable the auditing feature by selecting 'On' from the drop-down list.
Click Apply to save the information.