This appendix includes the following sections:
Deployment descriptors are BPEL process service component properties used at runtime by Oracle WebLogic Server, Oracle Enterprise Manager Fusion Middleware Control, or both. You set these properties during design time in the composite.xml file of the SOA composite application. Examples of deployment descriptor properties include completionPersistPolicy, inMemoryOptimization, oneWayDeliveryPolicy, transaction, nonBlockingInvoke, and others.
For more information about available deployment descriptor properties, see How to Define Deployment Descriptor Properties in the Property Inspector and Transaction and Fault Propagation Semantics in BPEL Processes.
Header manipulation and propagation are key business integration messaging requirements. You can set normalized message header properties during design time in the Properties tab of receive activities, invoke activities, OnMessage branches of pick and (for BPEL 1.1) scope activities, and reply activities. You can set properties for the following components:
Oracle JCA adapters
Oracle BPEL Process Manager
Oracle Web Services Addressing
Oracle B2B
REST adapters
For more information, see Propagating Normalized Message Properties Through Message Headers.
Oracle JCA adapters expose the underlying back-end operation-specific properties as header elements and allow for manipulation of these elements within a business process.
For more information about available Oracle JCA adapter message header properties, see the following guide:
Appendix A, "Oracle JCA Adapter Properties" of Understanding Technology Adapters for JCA adapter properties
Oracle BPEL Process Manager and Oracle Web Services Addressing rely extensively on header support to solve customers' integration needs.
For more information about available Oracle BPEL Process Manager and Oracle Web Services Addressing message header properties, see Propagating Normalized Message Properties Through Message Headers.
In Oracle B2B, you can manipulate headers with reserved key words.
For more information about available Oracle B2B message header properties, see Appendix, “Back-End Applications Interface" of User's Guide for Oracle B2B.
While most updates you make to the composite.xml file are performed from within the dialogs of the SOA Composite Editor during design time, other properties must be added manually to this file from within Source view. Table G-1 lists these properties and provides references to documentation that describes how to configure these properties.
Table G-1 Oracle SOA Suite Properties
| Property | Description | See... |
|---|---|---|
|
|
Specifies multiple partner link endpoint locations. This capability is useful for failover purposes if the first endpoint is down. |
|
|
|
Specifies the location of the fault policy file if it is different from the default location. This option is useful if a fault policy must be used by multiple SOA composite applications. |
|
|
|
Specifies the location of the fault binding file if it is different from the default location. This option is useful if a fault policy must be used by multiple SOA composite applications. |
|
|
|
By default, SOAP headers are not passed through by Oracle Mediator. To pass SOAP headers, add this property to the corresponding Oracle Mediator routing service. |
|
|
|
Specifies role names required to invoke SOA composite applications from any Java EE application. |
|
|
and
|
Specify these properties to stream attachments with SOAP. |
|
|
|
Specifies to override a local optimization setting for a policy. |
and Administering Oracle SOA Suite and Oracle Business Process Management Suite |
|
|
You can override the |
Administering Oracle SOA Suite and Oracle Business Process Management Suite |
|
|
Controls how faults and one-way messages are handled for one-way interface SOAP calls. |
|
|
|
Specifies the attachment size in bytes. |
Sending and Receiving MTOM-Optimized Messages to SOA Composite Applications |
A fault policy file defines fault conditions and their corresponding fault recovery actions. Each fault condition specifies a particular fault or group of faults, which it attempts to handle, and the corresponding action for it.
You can enter fault policy properties automatically through the Fault Policy Editor or manually in a fault policy framework file. Table G-2 lists these properties and provides references to documentation that describes how to configure these properties.
Table G-2 Oracle SOA Suite Fault Policy Properties
| Property | Description | See... |
|---|---|---|
|
|
Provides a delay between retries of an activity (in seconds). |
Manually Creating a Fault Policy File for Automated Fault Recovery |
|
|
Retries an activity a specified number of times. |
How to Design a Fault Policy for Automated Fault Recovery with the Fault Policy Wizard or Manually Creating a Fault Policy File for Automated Fault Recovery |
|
|
Specifies a time in seconds for the scheduler to wait before retrying. |
How to Design a Fault Policy for Automated Fault Recovery with the Fault Policy Wizard or Actions |
You can also enter adapter rejected message properties in the fault policy framework file during design time.
For more information, see Section "Error Handling" of Understanding Technology Adapters.
You can set most Oracle B2B properties on the Configuration tab of the Oracle B2B interface. These settings override property settings performed at Oracle Enterprise Manager Fusion Middleware Control.
For more information about available Oracle B2B properties, see Chapter "Configuring B2B System Parameters" of User's Guide for Oracle B2B.
You can configure Oracle Healthcare runtime and user interface, workflow notification, and normalized message header properties.
For more information about available Oracle Healthcare properties, see Healthcare Integration User's Guide for Oracle SOA Suite.
You can configure Oracle Business Activity Monitoring (BAM) business view properties.
For more information about Oracle BAM properties, see Monitoring Business Activity with Oracle BAM.
You can configure properties for the following components during runtime in the property pages of Oracle Enterprise Manager Fusion Middleware Control:
SOA Infrastructure
Oracle BPEL Process Manager
Human workflow notification and task service
Oracle Mediator
Cross references
Oracle B2B
Service and reference binding components (JCA adapters, web services, REST adapters, and Oracle Service Registry)
Global token variables and automatic database purging
You can configure properties for the SOA Infrastructure on the SOA Infrastructure Common Properties page. These property settings can apply to all SOA composite applications running in the SOA Infrastructure. The following types of properties can be set:
Audit level
Payload validation
Time duration during which to retrieve instances and faults data
Universal Description, Discovery, and Integration (UDDI) registry
Callback server and server URLs
BPM Analytics, BPEL sensors, and composite sensors
Java Naming and Directory Interface (JNDI) data source
Web service binding properties
Advanced configuration properties
For more information about available SOA Infrastructure properties, see Chapter "Configuring the SOA Infrastructure" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
You can configure BPEL process service engine properties on the BPEL Service Engine Properties page. These properties are used by the BPEL process service engine during processing of BPEL service components. The following types of properties can be set:
Audit trail level
Audit trail and large document thresholds
Payload schema validation
BPEL monitor and sensor enabling
Advanced configuration properties
For more information about available Oracle BPEL Process Manager properties, see Chapter "Configuring BPEL Process Service Components and Engines" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
You can configure human workflow notification and task service properties on the Mailer and Task tabs of the Workflow Notification Properties page. These properties are used by the human workflow service engine during processing of human workflow service components. The following types of properties can be set:
The notification mode for messages
The actionable addresses
The actionable email account name
The workflow session time out and custom class path URL values
The dynamic assignment and task escalation functions of the assignment service
Advanced configuration properties
For more information about available human workflow notification and task service properties, see Chapter "Configuring Human Workflow Service Components and Engines" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
You can configure Oracle Mediator properties. These properties are used by the Oracle Mediator service engine during processing of Oracle Mediator service components. The following types of properties can be set:
Audit level and metrics level
Parallel maximum rows retrieved
Parallel locker thread sleep
Custom configuration parameters
Container ID refresh time and container ID lease timeout
Resequencer locker thread sleep and maximum groups locked
Advanced configuration properties
For more information about available Oracle Mediator properties, see Chapter "Configuring Oracle Mediator Service Components and Engines" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
You can configure cross references to dynamically map values for equivalent entities created in different applications.
For more information about available cross reference properties, see Chapter "Managing Cross-References" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
You can enable Oracle B2B Dynamic Monitoring Service (DMS) metrics and configure advanced properties.
For more information about available Oracle B2B properties, see Chapter "Configuring Oracle B2B" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
You can configure the following service and reference binding component properties:
Activation specification (for services), interaction specification (for references), and endpoint properties (such as time outs, thresholds, maximum intervals, and others) for the JCA adapters
Web services properties such as enabling REST; enabling the WSDL, metadata exchange, and endpoint of the web service; and others
For more information about available service and reference binding component properties, see Chapter "Configuring Service and Reference Binding Components" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
You can configure additional properties in Oracle Enterprise Manager Fusion Middleware Control:
Define global token variables for specific URIs in SOA composite applications.
Enable automatic purging of large numbers of instances from the database.
For more information about token configurations, see the "Managing Global Token Variables for Multiple SOA Composite Applications" section of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
For more information, see the "Deleting Large Numbers of Instances with Oracle Enterprise Manager Fusion Middleware Control" section of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
The System MBean Browser of Oracle Enterprise Manager Fusion Middleware Control enables you to modify advanced properties that do not display in the property pages described in Property Pages. These advanced properties display beneath a link at the bottom of properties pages for the following components:
SOA Infrastructure
Oracle BPEL Process Manager
Oracle Mediator
Human workflow notification and task service
Oracle B2B
Note:
In addition to advanced properties, the same properties that display for modifying in the property pages described in Property Pages also display for modifying in the System MBean Browser.
The More SOA Infra Advanced Configuration Properties link at the bottom of the SOA Infrastructure Common Properties page enables you to display System MBean Browser advanced properties for the SOA Infrastructure. Properties that display for modifying include, but are not limited to, the following:
The maximum number of times an invocation exception can be retried
The number of seconds between retries for an invocation exception
The HTTP proxy authentication realm
The HTTP proxy authentication type
The HTTP proxy host
The password for HTTP proxies that require authentication
The HTTP proxy port number
The user name for HTTP proxies that require authentication
The HTTP protocol URL published as part of the SOAP address of a process in the WSDL file
The HTTPS protocol URL published as part of the SOAP address of a process in the WSDL file
The path to the Oracle SOA Suite keystore
For more information about available SOA Infrastructure System MBean Browser properties, see Chapter "Configuring the SOA Infrastructure" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
The More BPEL Configuration Properties link at the bottom of the BPEL Service Engine Properties page enables you to display System MBean Browser properties for the BPEL process. Properties that display for modifying include, but are not limited to, the following:
The extra BPEL class path to include when compiling BPEL-generated Java sources
The maximum number of times a failed expiration call (wait/onAlarm) is retried before failing
The delay between expiration retries
The size of the block of instance IDs to allocate from the dehydration store during each fetch
The number of invoke messages stored in in-memory cache
Whether one-way invocation messages are delivered
For more information about available Oracle BPEL Process Manager System MBean Browser properties, see Chapter "Configuring BPEL Process Service Components and Engines" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
The More Mediator Configuration Properties link at the bottom of the Mediator Service Engine Properties page enables you to display System MBean Browser properties for Oracle Mediator. Most of the System MBean Browser properties that display for Oracle Mediator can also be modified on the Mediator Service Engine Properties page.
For more information about available Oracle Mediator System MBean Browser properties, see Chapter "Configuring Oracle Mediator Service Components and Engines" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
The More Workflow Notification Configuration Properties link at the bottom of the Workflow Notification Properties page and the More Workflow Task Service Configuration Properties link at the bottom of the Workflow Task Service Properties page enables you to display System MBean Browser properties for human workflow. Properties that display for modifying include, but are not limited to, the following:
The address at which to receive incoming instant messages (IMs)
Whether to return custom notification service property names
For more information about available human workflow notification and task service System MBean Browser properties, see Chapter "Configuring Human Workflow Service Components and Engines" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.
The More B2B Configuration Properties link at the bottom of the B2B Server Properties page enables you to display System MBean Browser properties for Oracle B2B. Properties that display for modifying include, but are not limited to, Oracle B2B payload obfuscation.
For more information about available Oracle B2B properties, see Chapter "Configuring Oracle B2B" of Administering Oracle SOA Suite and Oracle Business Process Management Suite.