Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite
11g Release 1 (11.1.1.5.0)

Part Number E10226-09
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

3 Configuring the SOA Infrastructure

This chapter describes how to configure the properties of the SOA Infrastructure. These property settings can apply to all SOA composite applications running in the SOA Infrastructure.

This chapter includes the following topics:

For more information, see Section 1.2.1, "Introduction to the SOA Infrastructure Application."

3.1 Configuring SOA Infrastructure Properties

You can configure the following properties for the SOA Infrastructure:

The properties set at this level impact all deployed SOA composite applications, except those composites for which you explicitly set different audit level values at the composite application or service engine levels.

Additional advanced properties for the SOA Infrastructure can be configured through the System MBean Browser. To access these properties from the SOA Infrastructure menu, select Administration > System MBean Browser > Application Defined MBeans > oracle.as.soainfra.config.

To configure SOA Infrastructure properties:

  1. Access this page through one of the following options:

    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator... From the SOA Composite Menu...
    1. Select SOA Administration > Common Properties.
    1. Right-click soa-infra.
    2. Select SOA Administration > Common Properties.

    1. Select SOA Infrastructure Common Properties.

    The SOA Infrastructure Common Properties page displays the following properties.

    Note:

    Some property fields are designated with an icon showing green and red arrows. If you change these properties, you must restart the SOA Infrastructure.
    Description of soaadmin_common_props.gif follows
    Description of the illustration soaadmin_common_props.gif

    Descriptions for the properties at the top of the page are provided in the following table.

    Element Description
    Audit Level Select the level of information to be collected by the message tracking infrastructure. This information is collected in the instance data store (database) associated with the SOA Infrastructure. This setting has no impact on what gets written to log files.
    • Off: No composite instance tracking and payload tracking information is collected. No more composite instances can be created. No logging is performed. Note that disabling logging and the display of instances in Oracle Enterprise Manager Fusion Middleware Control can result in a slight performance increase for processing instances. Instances are created, but are not displayed.

    • Development: Enables both composite instance tracking and payload detail tracking. However, this setting may impact performance. This level is useful largely for testing and debugging purposes.

    • Production: Composite instance tracking is collected, but the Oracle Mediator service engine does not collect payload details and the BPEL process service engine does not collect payload details for assign activities (payload details for other BPEL activities are collected). This level is optimal for most normal production operations.

    Capture Composite Instance State Select to capture the SOA composite application instance state. Enabling this option may result in additional runtime overhead during instance processing. This option provides for separate tracking of the running instances. All instances are captured as either running or not running. This information appears later in the State column of the composite instances tables for the SOA Infrastructure and SOA composite application, where:
    • It shows the counts of running instances versus total instances

    • You can also limit the view to running instances only

    Valid states are running, completed, faulted, recovery needed, stale, terminated, and state not available.

    The running and completed states are captured only if this checkbox is selected. Otherwise, the state is set to unknown. The conditional capturing of these states is done mainly to reduce the performance overhead on SOA Infrastructure runtime.

    Note: If this property is disabled and you create a new instance of a SOA composite application, a new instance is created, but the instance does not display as running, faulted, stale, terminated, completed, or requiring recovery in the table of the Dashboard page of the composite application. This is because capturing the composite state of instances is a performance-intensive process.

    For example, if you enable this property and create an instance of a SOA composite application in the Test Web Service page, a new instance appears in the Dashboard page of the composite application. If you click Show Only Running Instances in the Dashboard page, the instance is displayed as running. If you then disable this property and create another instance of the same composite application, a new, running instance is created. However, if you then select Show Only Running Instances, the new instance is not listed in the table of running instances.

    In addition, to terminate a running instance, the instance must have a state (for example, running, faulted, and so on). This activates the Abort button on the Instances page of a SOA composite application. If this checkbox is not enabled before creating an instance, the Abort button is inactive, and you cannot terminate the instance.

    Payload Validation Select to enable validation of incoming and outgoing messages. Nonschema-compliant payload data is intercepted and displayed as a fault.

  2. Make changes appropriate to your environment.

    The UDDI Registry Properties section displays the following properties. You can integrate SOA composite applications running in the SOA Infrastructure with the UDDI registry. The UDDI registry provides a standards-based foundation for locating published services and managing metadata about services (security, transport, or quality of service). You can browse and select published services that meet your needs.

    The User and Password properties are applicable if the UDDI registry is secured. These are only used for the secure HTTP configuration of Oracle Service Registry (OSR). The Inquiry URL property is public.

    Element Description Example
    Inquiry URL Enter the URL of the master registry you want to query. The URL must not refer to the slave registry itself. Otherwise, you can lose some data. The inquiry URL obtains full-standard UDDI version 3 structures. This is the same UDDI inquiry URL that you specified in the Create UDDI Registry Connection wizard. http://master.mycompany.com:8888/registry/uddi/inquiry
    User Enter the registry inquiry user. admin
    Password Enter the password for the master registry inquiry user. Enter a password that utilizes good security practices.

    For information about setting the endpoint reference and service key, see Section 33.1.3, "Changing the Endpoint Reference and Service Key for Oracle Service Registry Integration."

  3. Make changes appropriate to your environment.

    The Server URLs section displays the following properties. If not explicitly set here, these values are determined at runtime by querying the Oracle WebLogic Server cluster, the web server, or the local server properties.

    Element Description
    Callback Server URL Enter the callback server URL. This URL is sent by the server as part of the invocation to a foreign service provider.
    Server URL Enter the server URL. This URL is published as part of the SOAP address of a service in the concrete WSDL file.

    Note: In 10.1.x releases, you manually configured SOAP optimization with the optSoapShortcut property. For release 11g, SOAP optimization is automatically configured. Therefore, if you upgrade to 11g and are using the optimized shortcut approach in existing applications, note that optimized calls are activated only when the hostname value (as referred to in the WSDL URL in the composite.xml file) matches the Server URL value. Either set both values to the hostname (for example, myhost) or to the full domain name (for example, myhost.domain.com). If these values do not match, a regular SOAP call is performed instead of an optimized local call.


    Note:

    If you change the Callback Server URL and Server URL values (for example, when moving from a test to a production environment), you must restart Oracle WebLogic Server for the WSDLs to be regenerated.
  4. Make changes appropriate to your environment.

    The Display Data Counts section displays the following properties for improving the time it takes to load pages.

    Note:

    Any changes to these properties impact all SOA farms associated with this Oracle Enterprise Manager instance.
    Element Description
    Disable fetching of instance and fault count metrics Select to disable the display of instance and fault count metrics on the following pages:
    • Dashboard pages of the SOA Infrastructure, SOA composite applications, service engines, and service components

    • Delete with Options: Instances dialog

    Instead, these metrics are replaced with links that you click to retrieve the instance and fault count metrics when you need this information. This setting can improve the time it takes to load pages.

    If you click a link to retrieve instance and fault count metrics, and Oracle Enterprise Manager Fusion Middleware Control times out, increase the transaction timeout property. For more information, see Section B.3, "Optimizing the Loading of Pages with Instance and Fault Metrics."

    Set default search criteria to fetch recent instances and faults only within a recent duration (applies to lists of instances and faults) Select this checkbox and specify a time period during which to retrieve recent instances and faults for display on the following pages:
    • Dashboard pages and Instances pages of the SOA Infrastructure, SOA composite applications, service engines, and service components

    • Dashboard pages of services and references

    • Faults and Rejected Messages pages of the SOA Infrastructure, SOA composite applications, services, and references

    • Faults pages of service engines and service components

    The time period you specify appears by default in the Fault Time From field on faults pages on which you can search for faults and the Start Time From field on instances pages on which you can search for instances.

    When you select this checkbox and specify a time period, the Show All links change to Show More links on the Dashboard pages of the SOA Infrastructure, SOA composite applications, service engines, and service components.


    For additional details, see Section 3.1.1, "Disabling Instance and Fault Count Metrics Retrieval with the System MBean Browser" for changing this property from the System MBean Browser and Section B.3, "Optimizing the Loading of Pages with Instance and Fault Metrics."

  5. Make changes appropriate to your environment.

  6. Expand the Advanced section.

    Description of soaadmin_common_props2.gif follows
    Description of the illustration soaadmin_common_props2.gif

    The Data Sources section displays the following properties. A data source enables you to retrieve a connection to a database server.

    Element Description Example
    Server Data Source JNDI Displays the JNDI location for the server data source. Click Configure to go to the data source configuration page of the Oracle WebLogic Server Administration Console. Global transaction support should be disabled for this data source. jdbc/SOALocalTxDataSource
    Server Transaction Data Source JNDI Displays the JNDI location for the server transactional data source. Click Configure to go to the data source configuration page of the Oracle WebLogic Server Administration Console. You must configure the data source for global transactions. jdbc/SOADataSource
    Nonfatal Connection Retry Count Enter the maximum number of times a nonfatal connection error can be retried before failing. These type of errors occur for any connection error with the dehydration store (for example, Oracle Real Application Clusters failover, database shutdown, and so on). 10

  7. Make changes appropriate to your environment.

    The Web Service Binding Properties section displays the following options.

    Element Description Example
    Oracle SSL Ciphers Enter the list of supported Oracle ciphers.

    A cipher suite is a set of algorithms that provide security for data transmissions. Before data can flow through an SSL connection, both sides of the connection must negotiate common algorithms to use.

    SSL_RSA_WITH_RC4_128_MD5
    Oracle Wallet Password Enter the wallet password for the keystore. Enter a password that utilizes good security practices.
    Use Chunking Select to enable chunking of data for SOAP over HTTP deliveries. - -
    Chunk Size Specify a chunk size. The value must be less than or equal to 999. The size is used for SOAP over HTTP deliveries and is specified in bytes. 500

  8. Make changes appropriate to your environment.

  9. Click Apply.

  10. If you make changes and want to reset these properties to their previous values, click Revert.

  11. To change advanced parameters, click More SOA Infra Advanced Configuration Properties. This opens the System MBean Browser. The properties that display include, but are not limited to, the following. Descriptions are provided for each property.

    • AuditConfig: The status of BPEL message recovery. By default, the bpelRecoveryStatus key is set to All for the AuditConfig property. If there are BPEL messages requiring recovery in the Recovery page of the BPEL process service engine, this setting enables a BPEL Message Recovery Required inline warning message and recovery icon to display in the Trace table of the Flow Trace page. If this key is set to Off, no message recovery information is displayed on the Flow Trace page. For more information, see Section 12.1, "Viewing the Audit Trail and Process Flow of a BPEL Process Service Component."

    • GlobalTxMaxRetry: The maximum number of times an invocation exception can be retried.

    • GlobalTxRetryInterval: The number of seconds between retries for an invocation exception.

    • HttpProxyAuthRealm: The HTTP proxy authentication realm.

    • HttpProxyAuthType: The HTTP proxy authentication type.

    • HttpProxyHost: The HTTP proxy host.

    • HttpProxyPassword: The password for HTTP proxies that require authentication.

    • HttpProxyPort: The HTTP proxy port number.

    • HttpProxyUsername: The user name for HTTP proxies that require authentication.

    • HttpServerURL: The HTTP protocol URL published as part of the SOAP address of a process in the WSDL file.

    • HttpsServerURL: The HTTPS protocol URL published as part of the SOAP address of a process in the WSDL file.

    • KeystoreLocation: The path to the Oracle SOA Suite keystore.

    • UddiCacheLifetime: The UDDI endpoint cache life span.

3.1.1 Disabling Instance and Fault Count Metrics Retrieval with the System MBean Browser

As described in Section 3.1, "Configuring SOA Infrastructure Properties," you can disable the retrieval of instance and fault count metrics in the Display Data Counts section of the SOA Infrastructure Common Properties page.

To disable instance and fault count metrics retrieval with the System MBean Browser.

You can also change this property through the System MBean Browser.

  1. Select Application Defined MBeans > emom.props > Server:AdminServer > Application: em > Properties > emoms.properties.

    Note that emoms.properties is only available for selection if you previously modified the Disable fetching of instance and fault count metrics option of the Display Data Counts section of the SOA Infrastructure Common Properties page.

  2. In the Name column of the Attributes tab, click Properties.

  3. In the Value column, expand Element_20.

  4. In the Element column, enter false to disable metrics retrieval.

  5. Click Apply.

  6. Restart the SOA Infrastructure. Note that a restart is not required if you instead change the Disable fetching of instance and fault count metrics option through the Display Data Counts section of the SOA Infrastructure Common Properties page.

3.2 Stopping and Starting the Managed Server and SOA Infrastructure

You can stop and start the SOA Infrastructure in Oracle Enterprise Manager Fusion Middleware Control for maintenance or for configuration restarts. To do so, stop and start the managed server on which the SOA Infrastructure is installed. This restarts both the managed server and the SOA Infrastructure.

Notes:

  • Starting with 11g Release 1 (11.1.1.4.0), you can no longer stop and start the SOA Infrastructure from the soa-infra menu in the navigator.

  • You can also have a developer configuration that only includes an administration server, and no managed servers.

To stop and start the managed server and SOA Infrastructure:

  1. Access this page through one of the following options:

    From the WebLogic Server Menu... From the WebLogic Domain Folder in the Navigator...
    1. Select Control.
    1. Right-click the managed server (for example, soa_server1).
    2. Select Control.


  2. To shut down the managed server and SOA Infrastructure, select Shut Down.

  3. Click OK when prompted to shut down the managed server and SOA Infrastructure.

  4. Wait for shutdown to complete.

  5. To start the managed server and SOA Infrastructure, select Start Up.

For information on stopping and starting managed servers with Node Manager, see Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.

For information on starting and stopping managed servers with WLST commands, see Oracle Fusion Middleware Administrator's Guide.

3.2.1 Waiting for SOA Infrastructure Startup Initialization to Complete

After the SOA Infrastructure is started, it may not be completely initialized to administer incoming requests until all deployed composites are loaded. Therefore, the response metrics that are displayed on some Oracle Enterprise Manager Fusion Middleware Control pages may not reflect their actual status. This is most apparent when the SOA Infrastructure is in a cluster with multiple managed servers and a large number of deployed composites.

During the initialization stage, Oracle Enterprise Manager Fusion Middleware Control does not prevent you from executing operations such as composite deployment, composite undeployment, and others, even though these operations may not complete successfully. Instead, a warning message is displayed at the top of the Oracle Enterprise Manager Fusion Middleware Control pages shown in Table 3-1. Do not perform operations such as composite deployment, composite undeployment, and others while this message is displayed. Once initialization completes, the message is no longer displayed. You see this after you refresh the page. You can then perform operations.

Table 3-1 SOA Infrastructure Initialization Message

This Warning Message Is Displayed... At the Top of These Pages...
Initializing SOA
Even though the soa-infra target is up, some SOA
Fabric components and composite applications are
still loading. You may need to allow some time for
the initialization to complete, and later click the
Refresh Page icon. It is not adivsable to execute
any operations on this soa-infra until this warning
goes away.
  • SOA Infrastructure home page

  • SOA composite application home page

  • Manage Partitions page

  • Partition home page


3.2.2 SOA Composite Application States and SOA Infrastructure Shutdown

SOA composite application states are not updated to indicate that they are down after SOA Infrastructure shutdown. If you attempt to access the composite, you receive an error message stating that composite details cannot be retrieved:

soa-infra runtime connection error  An error happened while connecting to
soa-infra runtime at  t3://152.61.150.106:8001/soa-infra.

This message may lead you to believe that another issue exists in the system. However, this is not the case.

These composite states display as up, or in some cases pending, because this metric indicates whether the composite is enabled, and is independent of whether the SOA Infrastructure is started. In addition, the composite is still active and can receive requests on other managed servers in a cluster.

3.2.3 Restarting the SOA Infrastructure Does Not Activate Endpoints When a Retired Composite is Activated

If a SOA composite application with adapter endpoints is in a retired state, the endpoints are not activated if you perform the following actions:

  • Restart the SOA Infrastructure

  • Activate the SOA composite application

This is because files, records, and so on are not picked up by the endpoint adapters. As a workaround, redeploy the SOA composite application after restarting the SOA Infrastructure.

3.2.4 SOA Infrastructure Startup Failure When cwallet.sso Includes the SOA Map

When cwallet.sso has the SOA map, you receive an error message similar to the following when attempting to start the SOA Infrastructure.

Caused By: java.security.UnrecoverableKeyException: Password verification 
failed 
        at 
sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:769) 
        at 
sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38) 
        at java.security.KeyStore.load(KeyStore.java:1185) 
        at oracle.j2ee.ws.saaj.util.SSLUtil.loadKeyStore(SSLUtil.java:73) 
        at 
oracle.j2ee.ws.saaj.util.SSLUtil.getKeyManagerFactory(SSLUtil.java:88) 
        at oracle.j2ee.ws.saaj.util.SSLUtil.getKeyManagers(SSLUtil.java:97) 
        at 
oracle.j2ee.ws.saaj.util.SSLUtil.createSSLSocketFactory(SSLUtil.java:50) 
        at 
oracle.integration.platform.common.SSLSocketFactoryManagerImpl.getSSLSocketFac 
tory(SSLSocketFactoryManagerImpl.java:58) 
        at oracle.fabric.common.wsdl.WSDLManager.init(WSDLManager.java:356) 
        at oracle.fabric.common.wsdl.WSDLManager.<init>(WSDLManager.java:101) 
        at 
oracle.fabric.common.metadata.MetadataManagerImpl.getWSDLManager(MetadataManag 
erImpl.java:283) 
        at 
oracle.fabric.composite.model.CompositeModel.getWSDLManager(CompositeM 

Perform the following steps to resolve this issue.

  1. Perform one of the following actions:

    • Delete the SOA map in cwallet.sso.

    • Remove $DOMAIN_HOME/config/fmwconfig/default-keystore.jks. Oracle Web Services Manager (OWSM) uses this file.

  2. Restart the SOA Infrastructure.

3.3 Changing the SOA Infrastructure Server URL Property Port

In addition to the SOA Infrastructure Common Properties page, you can also change the SOA Infrastructure ServerURL property port in the System MBean Browser of Oracle Enterprise Manager Fusion Middleware Control.

When changing the port, note the following details:

To change the SOA Infrastructure port:

  1. From the SOA Infrastructure menu, select Administration > System MBean Browser.

  2. Under Application Defined MBeans, expand oracle.as.soainfra.config > Server: server_soa > SoaInfraConfig > soa-infra.

    where server_soa is the name of the server provided during post installation configuration. By default, this name is soa_server1.

  3. In the Name column, click ServerURL.

    The Attribute: ServerURL page appears.

    Description of hwf_wlist_port.gif follows
    Description of the illustration hwf_wlist_port.gif

  4. In the Value field, change the port.

  5. Click Apply.

  6. Change the managed Oracle WebLogic Server port in the Oracle WebLogic Server Administration Console to the same value.

    In environments in which a load balancer is used in front of an Oracle WebLogic Server cluster, the ServerURL property host and port can be different from the Oracle WebLogic Server host and port. This is typical for enterprise deployment environments in which a load balancer distributes requests across the managed servers in the Oracle WebLogic Server cluster. For more details, see Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite.

3.4 Configuring Log Files

Oracle SOA Suite components generate log files containing messages that record all types of events, including startup and shutdown information, errors, warning messages, access information on HTTP requests, and additional information.

To configure log files:

  1. Access this page through one of the following options:

    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator...
    1. Select Logs > Log Configuration.
    1. Right-click soa-infra.
    2. Select Logs > Log Configuration.


    The Log Configuration page displays the following details:

    • 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.

    Description of sca_logconfig.gif follows
    Description of the illustration sca_logconfig.gif

  2. Perform the following log file tasks on this page:

    1. In the Logger Name column, expand a logger name. This action enables you to specify more specific logging levels within a component.

    2. In the Oracle Diagnostic Logging Level columns, select the level and type of information to write to a log file.

    3. 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 Administrator's 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.

    Description of sca_logfiles.gif follows
    Description of the illustration sca_logfiles.gif

    For more information about logging, see Oracle Fusion Middleware Administrator's 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/config/fmwconfig/servers/server_soa/logging.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\soa/servers/server_soa/logs/soa-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 Administrator's Guide.

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:

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.

  2. Under Domain Structure on the left side of the page, select Services > JDBC > Data Sources.

  3. In the Name column of the Data Sources table, select EDNDataSource (for event delivery network transactions) or SOADataSource (for all other types of transactions).

  4. Under the Configuration tab at the top, click the Transaction subtab.

  5. In the XA Transaction Timeout field, enter a value in seconds.

  6. Select the Set XA Transaction Timeout checkbox. You must select this checkbox for the new XA transaction timeout value to take effect.

  7. Click Save.