Deploying WebLogic Integration Solutions

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

wli-config.properties Configuration File

The wli-config.properties file controls various run-time characteristics of Oracle WebLogic Integration. The file is read when Oracle WebLogic Server starts. Oracle WebLogic Integration does not implement changes made to the file while Oracle WebLogic Server is running.

A related file, jws-config.properties, specifies domain-wide configuration parameters for the Oracle Workshop for WebLogic run-time engine.

The following table describes the contents and default settings of wli-config.properties.

Table C-2 Contents of wli-config.properties file
Property
Description
Default value
weblogic.wli.DocumentMaxInline
Size
Minimum size in bytes for documents stored in the SQL Document Store
524288
weblogic.wli.DocumentMaxIn
MemorySize
Maximum size in bytes of document buffered before writing to the SQL Document Store
524288
weblogic.wli.ProcessDocument
CleanupIntervalMinutes
Interval in minutes at which unreferenced documents are deleted from the SQL Document Store
20
weblogic.wli.SQLStoreLogSQ
Request that the SQL Document Store log its SQL requests to the Oracle Workshop for WebLogic debug log
false
weblogic.wli.OracleLog
Request an oracle.log in the domain directory
false
weblogic.wli.ProcessTypeMaxNameLength
Maximum size of process (workflow) type names, reflected in WLI system tables.

Note: Delete the default value and then leave the value for this property unspecified to get a value appropriate for the type of database in use.
200
weblogic.wli.PurgeRowNumMax
Maximum number of rows in the result set that returns instances ready to be purged
20
weblogic.wli.TrackingPurgeTxn
TimeMillis
Approximate transaction duration in milliseconds for purging tracking data
250
weblogic.wli.WliClusterName
In a domain with multiple clusters, this property represents the name of the cluster running the single WLI instance.

Note: Specify a cluster name only if running in a domain with multiple clusters.
None provided
wli.jmseg.EatSoapActionElement
When set to true, an event generator will consume the first element under the <SOAP:Body> element. This makes the event generator consistent with the JWS/JPD SOAP protocol, which uses the first element under the <SOAP:Body> element to bind to a method.
true


  Back to Top       Previous  Next