###################################################################### # DE Properties ###################################################################### # # This file is used to set up the properties for the Directory Engine. # # It supports the following parameters: # # monitor.enable (optional) # Tells the N2 framework that it should monitor this properties file for changes. # If omitted, it defaults to false. monitor.enable=true # monitor.interval (optional) # Tells the N2 framework with what frequency (in milliseconds) it should check # this file for modifactions. If omitted, it default to 5 seconds. # The max number of elements used within an SQL "in" clause. SqlInClauseLimit=900 # The batch size for saving, updating and retrieving resources. SqlBatchSize=50 # The size of the NamedEntity ID sequence cache. If omitted, it defaults to 50. NamedEntityCacheSize=50 # The size of the UserProperty ID sequence cache. If omitted, it defaults to 50. UserPropertyCacheSize=50 # The size of the cache for ExtensionInstance IDs. If omitted, it defaults to 10. ExtensionPointCacheSize=10 # The size of the cache for ExtensionInstance IDs. If omitted, it defaults to 20. ExtensionInstanceCacheSize=20 # Determines whether the comparison of entity names are to be case-insensitive - in such cases as RQL evaluation. # This applies to the comparisons made during the evaluation of RQL expressions. NameComparisonCaseInsensitive=false # Attribute allows users (mainly windows) to ignore case when logging in. # This emulates how a typical windows login is performed. IgnoreCaseOnLogin=false # The size of the cache for LDAP Container ID sequence numbers. If omitted, it # defaults to 50. LdapIDCacheSize=50 # The timeout period for the LDAP attributes cache - in milliseconds. A value # of zero, or less, disables the cache. LdapCacheTimeout=60000 # The maximum number of LDAP attributes to be cached. A value of zero, or # less, means no maximum is applied. LdapCacheMaxAttributes=500 # If a LDAP Directory supports paged search results, this is the maximum number # of entries to be returned in each page. A value of zero, or less, disables # paged searches. LdapSearchPageSize=500 # Holds a space-delimited list of the LDAP Attributes that are to be treated # as binary data. LdapBinaryAttributes= # Determines whether the comparison of LDAP DNs is case-insensitive or not. # Although the comparison of attribute names within an LDAP DN are always # case-insensitive, the values are (be default) case-sensitive. # Setting this property to true will mean that comparison of attribute values # within LDAP DNs will be case-insensitive. LdapDNCaseInsensitive=false # Refresh the Org Model caches by changing this property to true. To repeat the # reset change it back to false and then true again. ResetModelCache=false # Disables the processing of Push Destinations throughout Directory Engine. Any attempt to read a push # destination will result in no data being returned. Any attempt to modify or set a push destination # will result in an error being reported. DisableAllPushDestinations=false # Disables the processing of Push Destinations throughout Directory Engine but only for Resources. # Other organisational entities remain unaffected. See DisableAllPushDestinations for further details # of the behaviour. DisablePushDestinationsForResources=false # Enables, or disables, the Extension Point processing events. If disabled # no more events will be scheduled following the completion of any currently # scheduled event. # In a multi-node environment, only one node will chosen (at random) to # schedule and process the Extension Point processing events, if that node # is stopped, another node will be chosen to take over the scheduling and # processing. ExtensionPointProcessEnable=true # Enables, or disables, the automatic removal of those org-model entities # dynamically generated from the processing of ExtensionPoints. When this # property is true dynamically generated entities will be removed when # the LDAP entry/attribute from which they are derived is removed. # This property will only apply when ExtensionPointProcessEnable is true. # The default for this property is true - delete dynamically generated # org-model entities. ExtensionPointDeleteEnabled=true # The time of day (expressed in the JVM's default time-zone) at which the # first Extension Point processing will be scheduled. The accepted format # for this value is "hh:mm"; where "hh" is a value from 00 to 23, and "mm" # if a value from "00" to "59". # In a multi-node environment, only one node will chosen (at random) to # schedule and process the Extension Point processing events, if that node # is stopped, another node will be chosen to take over the scheduling and # processing. # Subsequent processing events will be scheduled according to the value of # the property ExtensionPointProcessInterval. ExtensionPointProcessStart=03:00 # The delay between the start of one Extension Point processing event and # the next. This value should be great enough to ensure that two events do # not overlap. # The value is expressed as an XML Schema Duration string. ExtensionPointProcessInterval=P0Y0M1DT0H0M0S # Enables, or disables, the processing of Resource Candidate Queries; to # automatically populate Positions and Groups with Resources, according to # configured LDAP Queries. # In a multi-node environment, only one node will chosen (at random) to # schedule and process the Candidate Query processing events, if that node # is stopped, another node will be chosen to take over the scheduling and # processing. AutoResourceGenEnable=true # Enables, or disables, the automatic deletion of those Resources deemed to # be invalid. A Resource is deemed to be invalid when the LDAP entry, from # which they originate, can no longer be found. When this property is # true invalid Resources will be removed when the LDAP entry from which # they are derived is removed. # The default for this property is false - DO NOT delete invalid Resources. # This property will only apply when AutoResourceGenEnable is true. AutoResourceDeleteEnabled=false # The time of day (expressed in the JVM's default time-zone) at which the # first Candidate Query processing will be scheduled. The accepted format # for this value is "hh:mm"; where "hh" is a value from 00 to 23, and "mm" # if a value from "00" to "59". # In a multi-node environment, only one node will chosen (at random) to # schedule and process the Candidate Query processing events, if that node # is stopped, another node will be chosen to take over the scheduling and # processing. # Subsequent processing events will be scheduled according to the value of # the property AutoResourceGenInterval. AutoResourceGenStart=03:30 # The delay between the start of one Candidate Query processing event and # the next. This value should be great enough to ensure that two events do # not overlap. # The value is expressed as an XML Schema Duration string. AutoResourceGenInterval=P0Y0M1DT0H0M0S # The number of dynamic query entities updated in a single database # transaction. Should be sufficiently large enough for performance but not # too large that the database transaction limit is reached. ResourceQueryBatchSize=50 # Selects the version of the RQL evaluation algorithm. Possible values are # 1: the original algorithm that resolves the RQL in-memory, retrieving # the resources as it traverses elements of the expression. # 2: translates the RQL to SQL and retrieves the resources in the final # SQL execution. In the majority of cases this is more efficient. # # When changing from v2 to v1 it will be necessary to perform a reset of # the RQL queries (in order to re-establish the internal query-model data). # To do this invoke the SOAP API ResourceQueryService.resetQueries. ResourceQueryVersion=2 # The size of the cache for Resource Query ID sequence numbers. ResourceQueryCacheSize=50 # The number of attempts to save a resource query in the database before # reporting failure. ResourceQueryRetryLimit=5 # The period to wait between retries if an attempt to save a resource query # in the database fails. # Specified in milliseconds. ResourceQueryRetryInterval=500 # Enables, or disables, the re-evalation of resource queries to identify if # those that are no longer referenced. If disabled automatic deletion of # un-referenced queries will not take place. In a multi-node environment, # only one node will be chosen (at random) to schedule and process the # re-evalation of resource queries, if that node is stopped, another node # will be chosen to take over the scheduling and processing. Processing # after node failover will commence after the next # ResourceQueryCleanerStart time - so there is likely to be a delay in # processing deletes. Note that changing this value will require a node # restart for the new value to take effect. ResourceQueryCleanerEnable=true # The time of day (expressed in the JVM's default time-zone) at which the # first resource query evaluation of those queries that can be deleted # will be scheduled. The accepted format for this value is "hh:mm"; where # "hh" is a value from 00 to 23, and "mm" if a value from "00" to "59". # In a multi-node environment, only one node will chosen (at random) to # schedule and process the re-evaluation events, if that node is stopped, # another node will be chosen to take over the scheduling and processing. # Subsequent processing events will be scheduled according to the value of # the property ResourceQueryCleanerInterval. Processing after node # failover will commence after the next ResourceQueryCleanerStart time - # so there is likely to be a delay in processing deletes. Note that # changing this value will require a node restart for the new value to # take effect. ResourceQueryCleanerStart=00:00 # The interval between re-evaluation of resource queries to identify those # that are no longer referenced such that they may be removed from the system. # This value should be great enough to ensure that two events do not overlap. # The value is expressed as an XML Schema Duration string. Note that changing # this value will require a node restart for the new value to take effect. ResourceQueryCleanerInterval=P1D # The time of day (expressed in the JVM's default time-zone) at which the # last resource query evaluation of those queries that can be deleted # will be accepted. The accepted format for this value is "hh:mm"; where # "hh" is a value from 00 to 23, and "mm" if a value from "00" to "59". # In a multi-node environment, only one node will chosen (at random) to # schedule and process the re-evaluation events, if that node is stopped, # another node will be chosen to take over the scheduling and processing. # Processing after node failover will commence after the next # ResourceQueryCleanerStart time - so there is likely to be a delay # in processing deletes. ResourceQueryCleanerEnd=01:00 # The number of dynamic query entities checked for deletion in a single # database transaction. Should be sufficiently large enough for performance # but not too large that the database transaction limit is reached. # The maximum value is 100 ResourceQueryCleanerLimit=100 # The number of seconds between deleting batches of dynamic query entities. # Permits time for other database transactions to occur some of which are # blocked whilst this operation is being performed. The minimum value is 1. ResourceQueryCleanerPause=5 # The number of attempts to update a resource in the database before reporting failure. ResourceModificationRetryLimit=5 # The period to wait between retries if an attempt to update a resource in the database fails. # Specified in milliseconds. ResourceModificationRetryInterval=500 # LDAP Alias to use for lookup of the system user. This alias can be # changed from the default system alias id a user wants to resolve the # above admin DN in an alias other than system. AdminLdapAlias=system # LDAP name to use and display for the admin user. The admin username by # default is tibco-admin; however this setting allows it to be any value. AdminLdapName=tibco-admin # The default sleep period in seconds for the DE prepare for undeploy thread PrepareForUndeployThreadSleep=60 # Determines whether the updates to user-settings are to be restricted when # the user's GUID is used as a storage-key. Also restricts updates if the # storage-key identifies a Workspace setting. restrictUserSettings=true