SOA Composite Application Properties
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 |