Logging Out of Oracle Enterprise Manager Fusion Middleware Control

Part III Administering the SOA Infrastructure This part describes how to administer the SOA Infrastructure. This part includes the following chapters: ■ Chapter 3, Configuring the SOA Infrastructure ■ Chapter 4, Monitoring the SOA Infrastructure 3 Configuring the SOA Infrastructure 3-1 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: ■ Section 3.1, Configuring SOA Infrastructure Properties ■ Section 3.2, Stopping and Starting the Managed Server and SOA Infrastructure ■ Section 3.3, Changing the SOA Infrastructure Server URL Property Port ■ Section 3.4, Configuring Log Files ■ Section 3.5, Changing the Driver Name to Support XA Drivers ■ Section 3.6, Specifying a Nondefault XA Transaction Timeout Value for XA Data Sources 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: ■ Audit level ■ Composite instance state to capture ■ Payload validation ■ Universal Description, Discovery, and Integration UDDI registry ■ Callback server and server URLs ■ Instance and fault count metrics retrieval ■ Search criteria for the retrieval of recent instances and faults ■ Java Naming and Directory Interface JNDI data source ■ Web service binding properties 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 3-2 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite 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: The SOA Infrastructure Common Properties page displays the following properties. Descriptions for the properties at the top of the page are provided in the following table. 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 . 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. Configuring the SOA Infrastructure 3-3 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. 3-4 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite 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. 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. Payload Validation Select to enable validation of incoming and outgoing messages. Nonschema-compliant payload data is intercepted and displayed as a fault. 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: 8888registryuddiinquiry 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. 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. Element Description