Appendix H The following BusinessEvents engine properties are either deprecated or are not used by BusinessEvents in this release.
Deprecated property. Ignored if present. In 3.0.0, this property specifies which of the following provided caching schemes to use: dist-unlimited-bs, dist-limited-bs, or dist-unlimited-nobs (default)Instead various properties are used to internally select the correct caching scheme, for example, be.engine.cluster.isCacheLimited and be.engine.cluster.hasBackingStoreSee Chapter 20, Configuring Cache Cluster Settings for more details. Deprecated Properties. If present work with In Memory OM fault tolerance, but has not purpose. These properties were introduced in a 2.x release to define a wait period, ensuring that cache was fully initialized before failing over to a secondary or failing back to the recovered primary. Deprecated property. Instead use Engine.FT.Weight for In Memory OM fault tolerance. (Unlike the currently used property, in this deprecated property, the lower the number the higher the priority.) Sets the country code to use for localization. Use upper case. Uses the ISO 3166 standard.Note: BusinessEvents is not fully localized in this release. Note: BusinessEvents is not fully localized in this release. Optional extension to the locale language, for example, if you set be.locale.language to en, you might set be.locale.variant to US, which is interpreted as en_USNote: BusinessEvents is not fully localized in this release. This property is ignored in BusinessEvents. The behavior is: log files are appended. to the end of the current log file when the BusinessEvents server starts. This behavior cannot be changed. This property is ignored in BusinessEvents. Instead the property Engine.Log.Dir is used. This property is ignored in BusinessEvents. Instead the property be.trace.log.maxnum is used.The Engine.Log.MaxNum property appears in the TRA file that is generated by TIBCO Administrator. In the TIBCO Administrator user interface, the value for this setting is added to the following location: the Server Settings tab of the merged BAR file instance. (The structure within the application configuration builder area is: application at the top level, then merged bar file, then merged bar file instance). This property is ignored in BusinessEvents. Instead the property be.trace.log.maxsize is used. java.property.tangosol.coherence.cacheconfig Not needed or used in this release except as advised by TIBCO Support.
Copyright © TIBCO Software Inc. All Rights Reserved.