BPEL Deployment Descriptor Config Properties

This document lists the config properties of some sections of the deployment descriptor. For each configuration property parameter, a description is given, as well as the expected behavior of the engine when it's changed.

PropertyName	Description	history	current state
completionPersistLevel	Set portion of the instance information that you want to save after the instance is completed. Possible values: "all" (default): meaning the instance is saved in both cube_instance and cube_scope tables. "instanceHeader", meaning Only the meta data of the instances are saved in cube_instance table. Note: this property can only be set if the "inMemoryOptimization" property is set to true.	since 10.1.2	active
completionPersistPolicy	This property configures how the instance data is saved. Possible values: "on" (default): the completed instance will be saved normally. "deferred": the completed instance will be saved, but with a different thread and in another transaction. "faulted": only the faulted instances will be saved. "off": no instances of this process will be saved.	since 10.1.2	active
defaultInput	the xml document that you want to use as input to test the process from the BPEL console	since 10.0.0	active
initializeVariables	Whether engine sets default value to variables. This eliminates the need for user to assign values to variables before doing XPath manipulation. Possible values: "true" (default): bpel engine will set default value to variable based on to-spec queries. "false": bpelc won't initialze the variables based on to-spec queries	since 10.0.0	active
inMemoryOptimization	Default value is false. This property can only be set to true if it does not have dehydration points. Activities like wait, receive, onMessage and onAlarm will create dehydration points in the process. If this property is set to true, engine will try to do inMemory optimization on the instances of this process. on to-spec queries	since 10.1.2	active
loadSchema	Default value is true, if set to false, we won't load any xml schemas basically the bpel will become type-less	since 10.0.1	active
noAlterWSDL	Default value is false, if set to true, the compiler will not try to modify the process WSDL to add binding and service information.	since 10.0.2 (It's used to be at the process level)	active
optimizeVariableCopy	Default value is true. If set to false, the engine don't enable our copy-on-write feature for assign copy	since 10.0.1	active
relaxTypeChecking	Default value is false. If set to true, compiler won't check type compatibility with assign activity.	since 10.0.1	active
relaxXPathQName	Default value is false. If set to true, compiler won't complain about unqualified steps in query. Example: where the correct form should be query="/ns1:payload/ns1:name", the following form will pass compilation if this flag is turned on: query="/payload/name".	since 10.0.1	active
sensorActionLocation	the location of the sensor action xml file that is used by ProcessConnect. Sensor action xml file configures the action rule for the events.	since 10.0.0	active
sensorLocation	the location of the sensor xml file. Sensor xml file defines the list of seonsors that BPEL engine will log events into.	since 10.0.0	active
testIntroduction	introduction text that will show up in the test console	since 10.0.0	active
transaction	when set to be "participate", the process will bubble up fault that is not handled by faultHandlers, which will calls the transaction to be rolled back.	since 10.0.0	active
SLACompletionTime	Service Level Agreement Completion Time - Threshold for a commitment that a process would be completed within a specified time period. Value is a XML duration.	since 10.0.0	active
xpathValidation	Default value is true. If set to false, compiler will not validate the xpath queries.	since 10.0.1	active
user	Security - the username a calling user must provide (given domain level security is on)	since 10.1.2.2	?
pw	Security - the password a calling user must provide (given domain level security is on)	since 10.1.2.2	?
role	Security - the role a calling user must belong to in the Identity Management (given domain level security is on)	since 10.1.2.2	?
deliveryPersistPolicy	The setting of persist policy of this process in the delivery layer. This setting override the same value in domain.xml. The possible values are:* "on": message into the system will be saved in delivery store before being picked up by the engine* "off": message into the system will be saved in memory before being picked up by the engine "off.immediate": the instance-initiating message won't be temporarily saved in delivery layer. Engine will use the save thread to initiate	since 10.1.3.3	active
keepGlobalVariables	When the instance is completed. Will engine keep the global variable values in the instance store. Possible values:* "false" (default): global variable values will be deleted when the instance completes "true": globale variables values will be kept in instance store	since 10.1.3.3	active

PropertyName	Description	history	state
basicHeaders	Security - creates HTTP-BASIC-AUTHENTICATION (values are propagate/ credentials) propagate: If the process has been invoked securely - these credentials are used for outbound too credentials: Pass credentials from descriptor	since 10.1.2.2	active
basicUsername	Security - the username - passed to basic authentication	since 10.1.2.2	active
basicPassword	Security - the credential - passed to basic authentication	since 10.1.2.2	active
callbackBindings	this is a list of bindings that the compiler will generate for the callback portType. The default value is "soap". You can set multiple bindings like "jms, soap". The first item will be used as the prefered binding when calling back.	since 10.0.1	active
correlation	If this is set to "correlationSet", this partnerLink is using bpel correlationSet. Default value is "wsAddressing".	since 10.0.0	deprecated
contentType	User can use this to set special http contentType. Ex: text/xml	since 10.0.0	deprecated sinse 10.1.3
httpAccept	overwrite the http 'accept' header that engine sends to the remote SOAP service	since 10.1.2	Axis only
httpContentType	overwrite the http 'content-type' header that engine sends to the remote SOAP service	since 10.1.2	Axis only
httpKeepAlive	If the server allows keepAlive connection, this boolean peroperty can be turned on to take advantage of it. Thus connections to the same server are shared between invocations. This attribute used to be named 'keepAlive'	since 10.1.2	Axis only
httpPassword	This is used for WSIF HTTP provider username/password authentication	since 10.0.0	active
httpUsername	This is used for WSIF HTTP provider username/password authentication	since 10.0.0	active
location	This is the URL that overrides the location defined in WSDL. In the case of SOAP over HTTP binding, this value overrides the SOAPAddress	since 10.0.0	active
nonBlockingInvoke	When this is set to be true, engine will spawn a separate thread to do the invocation so that the will not block the instance. The default value is false.	since 10.0.0	active
retryInterval	This is the number of seconds the engine wait between retries.	since 10.0.0	deprecated by Fault policy in 10.1.3.3
retryMaxCount	This is the number of retries the engine will attemp if an invoke failes because of network problems.	since 10.0.0	deprecated by Fault policy in 10.1.3.3
sendXSIType	Some old RPC style web services require the xsi:type to be set with every elements in the input message. If this value is set to be true, BPEL engine will populate the xsi:type of all the elements.	since 10.0.0	active
serviceProperties	XML element that will be passed to wsif provider	since 10.0.0	active
sendXSIType	Some old RPC style web services require the xsi:type to be set with every elements in the input message. If this value is set to be true, BPEL engine will populate the xsi:type of all the elements.	since 10.0.0	active
timeout	The number of seconds an soap call will timeout. A RemoteFault will be thrown if this happens.	since 10.0.0	Axis only
validateXML	Enables message boundary validation. When set to "true" the engine validates the xml message against the xml schema during and for this partnerLink. If the xml message is invalid then bpelx:invalidVariables runtime BPEL Fault is thrown. This overrides the domain level validateXML property. For example enable validation for only StarLoanService partner: http://:9700/orabpel/default/StarLoan/StarLoan?wsdl true	since 10.0.0	active
wsdlLocation	url of the WSDL file that defines this partnerLink. This property must be present. The BPEL compiler needs this to validate the BEPL source. This can be an abstract WSDL in the sense that only the portTypes and their dependencies need to be defined in the WSDL	since 10.0.0	active
wsdlRuntimeLocation	This is also a URL to the partnerLink WSDL. But it is used on the BPEL server, which means the concrete WSDL with all the service, port and binding definitions is needed. This property is optional, it defaults to the wsdlLocation property. This property also allows multiple URLs separated by blanks (space, new line and tabs). Thus the engine will try sequentially if any of them are not available.	since 10.0.0	active
wsseHeaders	Security - create a WS-Security UsernameToken (values are propagate/ credentials) propagate: If the process has been invoked securely - these credentials are used for outbound too credentials: Pass credentials from descriptor	since 10.1.2.2	active
wsseUsername	Security - the username for the token (required)	since 10.1.2.2	active
wssePassword	Security - the password for the token (optional)	since 10.1.2.2	active
preferredPort	the preferred port to use in case there are multiple WSDL ports availabel. The value is the NCName of the WSDL port.	since 10.1.3.3	active
fullWSAddressing	Default value is "false", when it's set to "true". WSDL will be generated to include full WSA headers in binding: "From", "Action", "To", "FaultTo"	since 10.1.3.3	active