SOA Composite Application States and SOA Infrastructure Shutdown SOA Infrastructure Startup Failure When cwallet.sso Includes the SOA Map

Configuring the SOA Infrastructure 3-13 ■ A View list for selecting the type of loggers for which to view information: – Persistent: Loggers that become active when a component is started. Their configuration details are saved in a file and their log levels are persisted across component restarts. – Active runtime: Loggers that are automatically created during runtime and become active when a particular feature area is exercised for example, oracle.soa.b2b or oracle.soa.bpel. Their log levels are not persisted across component restarts. ■ A table that displays the logger name, Oracle Diagnostic Logging ODL level for setting the amount and type of information to write to a log file, the log file, and the log level state. 2. Perform the following log file tasks on this page:

a. In the Logger Name column, expand a logger name. This action enables you

to specify more specific logging levels within a component.

b. In the Oracle Diagnostic Logging Level columns, select the level and type of

information to write to a log file.

c. In the Log File column, click a specific log file to create and edit log file

configurations. For more information about ODL log files and the level and type of logging information to write to a log file, see Oracle Fusion Middleware Administrators Guide.

3. Click the Log Files tab.

This page enables you to create and edit log file configurations, including the log file in which the log messages are logged, the format of the log messages, the rotation policies used, and other parameters based on the log file configuration class. 3-14 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite For more information about logging, see Oracle Fusion Middleware Administrators Guide. For information on setting logging levels and Oracle SOA Suite logging files to view, see Section B.13, Setting Logging Levels for Troubleshooting.

3.4.1 Configuring the Logging File Encoding Property

The oracle-soa-handler log handler property of the soa-diagnostic.log file has no encoding property specified in the SOA_ Domain configfmwconfigserversserver_soalogging.xml file. Instead, the soa-diagnostic.log file is written in the operating system’s default encoding format. This can cause the following problems: ■ Non-ASCII error messages can become unreadable because logging information is written to soa-diagnostic.log in the server’s default encoding format. ■ On Windows operating systems, writing in the default encoding format can lead to non-ASCII data loss. To avoid this problem, specify a value of UTF-8 for the oracle-soa-handler log handler property in the logging.xml file. ?xml version=1.0? logging_configuration log_handlers log_handler name=wls-domain class=oracle.core.ojdl.weblogic.DomainLogHandler level=WARNING log_handler name=oracle-soa-handler class=oracle.core.ojdl.logging.ODLHandlerFactory property name=path value=c:\soa1210.1411\user_ projects\domains\soaserversserver_soalogssoa-diagnostic.log property name=maxFileSize value=10485760 property name=maxLogSize value=104857600 property name=supplementalAttributes value=J2EE_APP.name,J2EE_ MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name,composite_instance_id,component_ instance_id,composite_name,component_name property name=encoding value=UTF-8 log_handler log_handlers ... Log files are written with ODL. You can view the content of log files from Oracle Enterprise Manager Fusion Middleware Control. For more information about logging, see Oracle Fusion Middleware Administrators Guide.