Changing the SOA Infrastructure Server URL Property Port

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. Configuring the SOA Infrastructure 3-15

3.5 Changing the Driver Name to Support XA Drivers

If your data sources require support for XA drivers, you must change the driver name on Oracle WebLogic Server. This is particularly true for environments in which BPEL processes assume XA is present when calling database adapters and JMS adapters. To change the driver name through one of the following methods: ■ Edit in Oracle WebLogic Server Administration Console. 1. Log into Oracle WebLogic Server Administration Console.

2. In the left pane, select Domain Structure.

3. Select Services JDBC Data Source SOADataSource Connection Pool.

4. For the Driver Class Name, change the value to

oracle.jdbc.xa.client.OracleXADataSource. This provides support for the XA driver. 5. Restart the server. ■ Edit the SOADataSource-jdbc.xml file. 1. Open the soaDataSource-jdbc.xml file on Oracle WebLogic Server. 2. Change the SOADataSource driver name from oracle.jdbc.OracleDriver to oracle.jdbc.xa.client.OracleXADataSource. ?xml version=1.0 encoding=UTF-8? jdbc-data-source . . . . . . nameSOADataSourcename jdbc-driver-params urljdbc:oracle:thin:adc60086fems.us.oracle.com:1537:co0yd570url driver-nameoracle.jdbc.xa.client.OracleXADataSourcedriver-name properties property nameusername valuefusion_soainfravalue property properties . . . . . . jdbc-driver-params . . . . . . jdbc-data-source

3.6 Specifying a Nondefault XA Transaction Timeout Value for XA Data Sources

The default XA transaction timeout value for XA data sources is 0 seconds. You can change the default value in the Oracle WebLogic Server Administration Console. Follow these steps. To specify a nondefault XA transaction timeout value for XA data sources: 1. Log in to Oracle WebLogic Server Administration Console.