2025

Fabasoft Folio KernelPermanent link for this heading

The following variables apply to the Fabasoft Folio Kernel.

DirectoriesPermanent link for this heading

Following variables define directory settings:

  • GLOBALDATADIR
    The path of the directory in this variable determines where data that is required for all users of the Fabasoft Folio Services on this machine can be stored. This directory is used as root directory for CASCACHEDIR, INSTALLDIR and STATICDIR, unless these variables are defined. The default value is /var/opt/fabasoft/cache on Linux systems and %ProgramData%\Fabasoft on Microsoft Windows.
  • CASCACHEDIR
    The path of the directory in this variable determines where the cache of the CAS areas is stored.
  • INSTALLDIR
    Path of the directory where files of software components can be stored during the installation.
  • STATICDIR
    Path of the directory where the static object model is stored.
  • LOCALDATADIR
    Path of the directory where data of the Fabasoft Folio Services can be stored.
    In a Microsoft Windows environment the default value is %ProgramData%\Fabasoft. On Linux systems it is /var/opt/fabasoft/cache. This directory is used as root directory for CACHEDIR and COMMITDIR and DOCDIR, unless these variables are defined.
  • CACHEDIR
    Path of the directory where the zero-downtime cache is stored.
  • COMMITDIR
    Path of the directory where the ID cache is stored.
  • DOCDIR
    Path of the directory where the cached contents are stored.
  • DIRECTORYSEPERATENAME
    This variable serves to save a string in the environment that is used to structure directories (e.g. CACHEDIR, COMMITDIR).
  • TEMPDIR
    Path of the directory where the temporary files are stored. The default value is /tmp/Fabasoft on Linux systems and %TEMP%\Fabasoft on Microsoft Windows.
  • ENABLECONTENTRESTRICTPATH (TRUE/FALSE)
    With this option, the restriction on file system paths for contents can be disabled. By default, only paths beneath TEMPDIR and DOCDIR are allowed for reading and writing contents by unprivileged methods.
  • CONTENTRESTRICTPATHRW
    A list of directories separated by the path separator to additionally allow paths for reading and writing contents.
  • CONTENTRESTRICTPATHRO
    A list of directories separated by the path separator to additionally allow paths for reading contents.

PreparePermanent link for this heading

Following variables define installation settings:

  • CHECKINSTALLATION
    The value of this variable determines whether software components should be updated automatically or not.
    • YES
      Default value of this variable. Fabasoft Folio Kernel and software components are installed or updated and the value of the INSTALLDIR variable is set.
    • COMPONENTS
      Only software components are updated automatically. This mode is used if the trace kernel was installed.
    • NO
      Neither the Fabasoft Folio Kernel nor the software components are updated. In this case all .DLL files have to be in one directory or found via the system environment variable PATH.
    • KERNEL
      Only the Fabasoft Folio Kernel is updated automatically.
    • SIMPLE
      Neither the Fabasoft Folio Kernel nor the software components are updated. The “dll” files can be located in the component directory (environment variable INSTALLDIR).
    • SEARCH
      Fabasoft Folio Kernel and software components are updated where they are found in the local system and if they are not found they are installed in the default directory.
  • The following environment variables serve as strings transferred during an automatic software update:
    • COOPREP_BOOTSTRAP
    • COOPREP_COMMAND
    • COOPREP_INSTALL
    • COOPREP_PREPARE
    • COOPREP_TITLE
    • COOPREP_UNINSTALL
  • COMPLETE (TRUE/FALSE)
    During the installation of a Fabasoft software product single software components can be chosen. This means that a complete installation does not have to be executed.
    However, if the value of the variable COMPLETE is set to TRUE, all selected software products are installed completely.
  • EXTERNALUPGRADE (TRUE/FALSE)
    This variable determines whether the file cooupgr*.dll is used during an upgrade of the Fabasoft Folio Kernel or not.
  • UPDATE (TRUE/FALSE)
    Repeated registration of files of the software components so that controls are entered in the Microsoft Windows Registry. This parameter is also used when performing a software update. The option can be specified as command line argument to the cooprep utility.

Connection SettingsPermanent link for this heading

Following variables define connection settings:

  • -hostcoost
    -host
    INETHOSTCOOST
    HOSTCOOST
    INETHOST
    HOST
    Hostname or IP address of the machine where the primary COO service of the Fabasoft Folio Domain is located. This is determined during the installation process. The options are listed in evaluation order, command line options start with a dash, environment variables and registry settings are listed all upper case.
  • -portcoost
    -port
    INETPORTCOOST
    PORTCOOST
    INETPORT
    PORT
    In this environment variable the TCP/IP port number of the primary COO service of the Fabasoft Folio Domain is declared. The options are listed in evaluation order, command line options start with a dash, environment variables and registry settings are listed all upper case.
  • CONNTIME
    Timeout value when a connection from the Fabasoft Folio Kernel to the Fabasoft Folio Backend Services is established. If this time interval (declared in seconds) is exceeded before the connection is established, an error message is displayed.
    Default value: 5 s
  • RESPTIME
    To establish a valid connection between the Fabasoft Folio Kernel and the Fabasoft Folio Backend Services, first the kernel has to send a request to the backend services and then the backend services have to send a response to the kernel.
    The time that elapses before the confirmation from the backend services is received by the kernel is checked, and the value of the variable RESPTIME is considered as the maximum time interval. If this is exceeded an error message is displayed.
    Default value: 15 s

The following variables deal with communication between the Fabasoft Folio Kernel and the Fabasoft Folio COO Service:

  • COORETRYCOUNT
    This variable determines how often an operation is repeated after an error.
    Default value: 1
  • COORETRYMIN
    Minimum time interval after which an operation can be repeated again.
    Default value: 100 ms
  • COORETRYMAX
    Maximum time interval after which an operation has to be repeated again.
    Default value: 500 ms
  • COORETRYTIMEOUT
    If an error occurs during the execution of an operation after the time interval specified in this variable, the operation is not repeated again.
    Default value: 5000 ms
  • COOMAXRECHECKTIMEOUT
    If a local service is unavailable, it is rechecked after this timeout.
    Default value: 5000 ms

The following variables deal with the communication between the Fabasoft Folio Kernel and the Fabasoft Folio MMC Service:

  • MMCRETRYCOUNT
    Default value: 1
  • MMCRETRYMIN
    Default value: 100 ms
  • MMCRETRYMAX
    Default value: 500 ms
  • MMCRETRYTIMEOUT
    Default value: 5000 ms
  • MMCMAXRECHECKTIMEOUT
    If a local service is unavailable, it is rechecked after this timeout.
    Default value: 5000 ms

The following variables deal with event log messages in the communication between the Fabasoft Folio Kernel and the Fabasoft Folio Backend Services:

  • RPCTHRESHOLDTIME
    When executing RPCs an information message (Slow RPC call) can be created in the event log after a defined duration of the RPC. This variable contains the time interval after which the event log entry is created.
    Default value: 10 s
  • COOTHRESHOLDTIME
    If an RPC is sent to a Fabasoft Folio COO Service a warning can be created in the event log after a defined duration of the RPC. This variable contains the time interval after which the event log entry is created.
    Default value: 20 s
  • MMCTHRESHOLDTIME
    If an RPC is sent to a Fabasoft Folio MMC Service a warning can be created in the event log after a defined duration of the RPC. This variable contains the time interval after which the event log entry is created.
    Default value: 20 s
  • RPCTHRESHOLDSIZE
    When executing RPCs an information message can be created in the event log when the RPC exceeds a specified size of data. This variable contains the size of data when the event log entry is created.
    Default value: 500000 bytes
  • COOTHRESHOLDSIZE
    If an RPC is sent to a Fabasoft Folio COO Service a warning can be created in the event log when the RPC exceeds a specified size of data. This variable contains the size of data when the event log entry is created.
    Default value: 2000000 bytes
  • MMCTHRESHOLDSIZE
    If an RPC is sent to a Fabasoft Folio MMC Service a warning can be created in the event log when the RPC exceeds a specified size of data. This variable contains the size of data when the event log entry is created.
    Default value: 5000000 bytes

TransactionsPermanent link for this heading

The following variables concern the execution and validity of transactions:

  • TRANSACTIONRETRYCOUNT
    This variable determines how often a transaction is repeated after an error.
    Default value: 2
  • TRANSACTIONRETRYMIN
    Minimum time interval after which a transaction can be repeated.
    Default value: 500 ms
    Note: A transaction is repeated after a randomly chosen time interval in the range of the values TRANSACTIONRETRYMIN and TRANSACTIONRETRYMAX.
  • TRANSACTIONRETRYMAX
    Maximum time interval after which a transaction can be repeated.
    Default value: 2000 ms
    Note: A transaction is repeated after a randomly chosen time interval in the range of the values TRANSACTIONRETRYMIN and TRANSACTIONRETRYMAX.
  • TRANSACTIONSKEWLEVEL
    In some cases, especially with web transactions, it is possible that time at which the transaction ends is earlier than the time of the start of the transaction. The value in the TRANSACTIONSKEWLEVEL variable determines the difference between start and end time of a transaction in the case that the end time is earlier than the start time so that the transaction is valid.
    Default value: 600 s (10*60 s)
  • TRANSACTIONDISCARDTIME
    Transactions can run over a long period of time. The value of this variable specifies a maximum time interval in which a commit of the transaction may be regarded as valid.
    Default value: 172 800 s (48*60*60 s)
  • TRANSACTIONRECHECKTIME
    If a transaction is executed, the security settings of the user in whose context the transaction is running are rechecked after a certain time interval.
    Default value: 21 600 s (6*60*60 s)
  • TRANSACTIONAUTOLOCK (TRUE/FALSE)
    If set to TRUE and an object that has not been locked should be modified, an automatic lock is applied to the object.
    Default value: TRUE
  • TRANSACTIONFORCELOCK (TRUE/FALSE)
    If set to TRUE and an object that has not been locked should be modified, an error is generated. TRANSACTIONFORCELOCK=TRUE overrides TRANSACTIONAUTOLOCK=TRUE.
    Default value: FALSE

Distributed TransactionsPermanent link for this heading

Following variables define distributed transaction settings:

  • ENABLEDTM (TRUE/FALSE)
    With this option, the usage of the Fabasoft Distributed Transaction Manager (DTM) for the execution of distributed transactions (in case of Oracle Database and PostgreSQL) can be disabled. If this parameter is set to FALSE, no 2-phase-commit protocol is used for distributed transactions. By default, the setting in the property Enable 2-Phase Commit in the current domain is used.
  • ENABLEDTC (TRUE/FALSE)
    With this option, the usage of the Microsoft DTC for the execution of distributed transactions can be disabled. If this parameter is set to FALSE, no 2-phase-commit protocol is used for distributed transactions. By default, the setting in the property Enable 2-Phase Commit in the current domain is used.
  • LOCALDTC (TRUE/FALSE)
    The Microsoft DTC is installed on the Fabasoft Folio Backend Server to which the single Fabasoft Folio Web Clients connect. In doing so, the installation on the single client machines is not necessary.
  • SPECIFICDTC
    Using this variable, a machine where a DTC is installed and that is used for the execution of distributed transactions can be specified.
  • SEARCHDTC (TRUE/FALSE)
    If this variable is set to TRUE, there is an automatic search for a DTC when distributed transactions are executed.
  • RANDOMDTC (TRUE/FALSE)
    If multiple DTCs are installed in a network choose a DTC to be used for distributed transactions at random by setting this variable.

Object LockingPermanent link for this heading

  • SIMPLELOCK (TRUE/FALSE)
    If this variable is set to TRUE, locks which are automatically unlocked on commit/abort are not stored within the database. By default, this setting is disabled.

The following variables are used for extended error search e.g. in problems with locked objects:

  • LOCKTIMEOUTSLEEP
    5 ms
  • LOCKTIMEOUT1
    50000 ms
  • LOCKTIMEOUT2
    2000 ms
  • LOCKTIMEOUT3
    4000 ms
  • LOCKTIMEOUT4
    200 ms
  • LOCKTIMEOUT5
    10000 ms
  • LOCKTIMEOUT6
    1000 ms
  • LOCKTIMEOUTLEVEL
    5000 ms
  • LOCKTIMEOUTRESOLUTION
    32 ms
  • LOCKTIMEOUTMODE
    0

Object LoadingPermanent link for this heading

Following variables define settings concerning object loading:

  • REFRESHBLOCKLEVEL
    If a large number of objects is refreshed an entry in the event log is created. This variable contains the number of objects when an event log entry is created. The event log entries can help to detect performance problems.
    Default value: 5000
  • LOADBLOCKLEVEL
    If a large number of attributes is loaded an entry in the event log is created. This variable contains the value of the number of objects when an event log entry is created.
    Default value: 5000
  • REFRESHBLOCKMAX
    If a large number of objects is refreshed this is performed block by block. This variable contains the number of objects that are refreshed in one RPC (in one block) at maximum.
    Default value: 25000
  • LOADBLOCKMAX
    If a large number of attributes is loaded this is performed block by block. This variable contains the number of objects that are loaded in one RPC (in one block) at maximum.
    Default value: 25000
  • LOCALOBJECTSLIMIT
    With the help of this variable it can be defined how many objects are deposited in the Commonly Used list (in objects of the class Working environment).
    Default value: 1000
  • LOCALOBJECTSLEVEL
    This variable defines the limit value which determines whether the Commonly Used list (in objects of the class Working Environment) is resorted when objects are reused or if the order is retained.
    Basically, objects are added at the end of the list. If the maximum number of objects in the object list is already reached, the first object is deleted from the list. If the list contains less than LOCALOBJECTSLEVEL objects, and an object which is already in the list is reused there is no resorting. Otherwise, if the list is already filled with more objects than defined in the variable LOCALOBJECTSLEVEL, and an object placed in the first LOCALOBJECTSLEVEL objects is reused, then this object is ranked backwards.
    Default value: 500
  • LOADCOMPLETE
    This variable defines if the Fabasoft Folio Kernel loads all attributes of an object or only a certain set of standard attributes which means a second RPC is needed if other attributes are requested.
    Default value: true
  • LOADCOMPLETELIMIT
    This variable defines how many objects are loaded completely if access via object pointer property.
    Default value: 250
  • LOADFOLLOW
    This variable defines if the object pointer properties of an object are implicitly loaded.
    Default value: false
  • LOADOBJECTBLOB
    This variable defines if the Fabasoft Folio Kernel requests the Fabasoft Folio Server cache entry and processes it itself to decrease the COO service load by distributing it.
    Default value: true

QueriesPermanent link for this heading

To arrange searching efficiently, values in the following variables are considered:

  • QUERYRESTRLEVEL
    When executing a search, the objects which are found are passed to the client and a check of the ACL is executed for each single object (if the user has the right to search for this object). Depending on the rights that are allocated in the ACL, the objects are either shown or refused for the concerned user. If the number of checked objects exceeds the value in the variable QUERYRESTRLEVEL, an additional check of the search’s efficiency is executed. (see QUERYRESTRFACTOR).
    Default value: 5000
  • QUERYRESTRFACTOR
    After the number of objects defined in the variable QUERYRESTRLEVEL is checked, additionally the efficiency of the search is checked. This works with following formula:
    displayed objects * QUERYRESTRFACTOR < refused objects
    If the number of objects that a user is not allowed to search for is bigger than the number of objects that a user is allowed to search for multiplied by the value of the variable QUERYRESTRFACTOR, an error message is displayed.
  • QUERYSUBQUERYMAX
    When a full-text search or a search containing a sub-query is carried out (for example, a query containing a SELECT statement within another SELECT statement or sub-queries for the optimization of back-links or referenced properties), and the number of matches is greater than the specified value in this variable then the Fabasoft Folio Kernel generates the error message QLPERR_INEFFICIENTSUBQUERY. The results that are returned until this error is generated can however be subsequently used.
    Default value: 100000
  • QUERYTHREADMAX
    This variable defines the maximum number of parallel COO service queries triggered by a single Fabasoft Folio query.
    Default value: 4

MMCPermanent link for this heading

Following variables define MMC settings:

  • MMCTEMPCLEANUPINTERVAL
    This variable defines the time interval in minutes of the recurring clearance process of the MMC area temporary directory. The default value of this variable is 120.
  • MMCREADVERIFYHASH (TRUE/FALSE)
    This variable defines if the hash should be verified when loading the content. This option only takes effect when the Fabasoft Folio Kernel is configured for direct MMC area access. The default value of this variable is TRUE.
  • MMCWRITETHREADCOUNT
    This variable defines the maximum number of threads writing parallel to a CAS area. This option only takes effect when the Fabasoft Folio Kernel is configured for direct MMC area access. The default value of this variable is 12.
  • MMCREADDIR_<areaname>
    This variable defines a preferred read file share for a dedicated MMC area, if multiple file shares are configured for direct MMC area access.

CAS CachePermanent link for this heading

Following variables define CAS cache settings:

  • ENABLECASCACHEDIR (TRUE/FALSE)
    Determines whether the Fabasoft Folio Kernel use a cache for CAS areas.
  • CASCACHEMAXMB
    This variable defines the maximum size of the CAS cache identified by CASCACHEDIR. The default value of this variable is 1024.
  • CASCACHECLEANUPINTERVAL
    This variable defines the time interval in minutes of the recurring clearance process of the CAS cache considering the value of CASCACHEMAXMB. The default value of this variable is 120.

CachePermanent link for this heading

Following variables define cache settings:

  • CACHECLEANUPRECHECKTIME
    If the Fabasoft Folio Kernel performs an aggressive cache cleanup, a warning can be created in the event log after a defined duration. This variable contains the time interval used for generating event log entries for an ongoing aggressive cache cleanup after the threshold time has been exceeded.
    Default value: 600 s
  • CACHECLEANUPTHRESHOLDTIME
    If the Fabasoft Folio Kernel performs an aggressive cache cleanup, a warning can be created in the event log after a defined duration. This variable contains the time interval after which the event log entry is created. Long and recurring periods of aggressive cache cleanups indicate a cache size limit that could be too small for the workload.
    Default value: 60 s
  • CACHEMODIFY (TRUE/FALSE)
    If this variable is set to FALSE, information in the client cache cannot be modified.
  • CACHEPERSIST (TRUE/FALSE)
    If this value is set to FALSE, the client cache can be read and modified, but the modifications are not saved.
  • CACHESIZE
    This entry stores the value of objects that can be saved in the cache at maximum. The default value of the variable CACHESIZE for the Fabasoft Folio Kernel is 20000 objects. The default value for a Fabasoft Folio Web Service is 20000 objects for a 32-bit installation and 50000 objects for a 64-bit installation.

External CachePermanent link for this heading

Following variables define external cache settings:

  • ECSCONNECTSTRING
    Defines the connection string for the external cache. If it is set to a valid string the Fabasoft Folio Kernel will try to connect to the external cache service and receive objects from there. Only if no object or an outdated object is found, the Fabasoft Folio COO Service will be contacted.
    No default value, empty
  • ECSKEYPREFIX
    If multiple independent Fabasoft Folio Kernel installations are accessing the same external cache it is suggested to use a unique key prefix to avoid key collisions. Typical and suggested key prefixes are e.g. “/r/r/<host-name>”
    No default value, empty
  • ECSVALIDATECHANGEDAT
    If the Fabasoft Folio Kernel performs an external cache access and receives an object this environment variable decides if the received object should be checked for having the correct objchangedat. To ensure the kernel is working with the correct version of the object this should be set to TRUE. Only for performance comparison reasons it makes sense to set it temporarily to FALSE.
    Default value: TRUE

JavaPermanent link for this heading

Following variables define Java settings:

  • JAVAHEAPSIZEINIT
    When using Java implementations, the defined initial and minimum Java heap size is crucial for functionality and performance. The default value is 64m (corresponds to –Xms64m).
  • JAVAHEAPSIZEMAX
    When using Java implementations, the defined maximum Java heap size is crucial for functionality and performance. The default value is 256m (corresponds to –Xmx256m).
  • JAVAPERMHEAPSIZEMIN
    When using Java implementations, the defined initial and minimum Java permanent generation heap size is crucial for functionality and performance. The default value is 32m (corresponds to -XX:PermSize=32m).
  • JAVAPERMHEAPSIZEMAX
    When using Java implementations, the defined maximum Java permanent generation heap size is crucial for functionality and performance. In case of OutOfMemoryError occurrences with the exception message “PermGen space”, consider increasing the value. The default value is 128m (corresponds to -XX:MaxPermSize=128m).
  • JAVAENABLEOUTPUT
    When using Java implementations, System.out and System.err output is not forwarded to the process by default. For debugging purposes, output can be enabled using this Boolean variable.
    Default value: false
  • COOJAVA_JVMOPTIONS
    In this variable arbitrary JVM options can be passed to the Java virtual machine.

Error LoggingPermanent link for this heading

Following variables define error logging settings:

  • ERRORMODE
    With this variable it can be specified which errors cause entries in a “log” file.
    • Normal
      Only grave errors are logged.
    • Off
      No errors are logged.
    • All
      All errors are logged.
  • ERRORLOG
    Path of the file in which errors are logged.
  • LOGDATACONSISTENCIES (TRUE/FALSE)
    If enabled (default) data inconsistency errors are logged into the event log.

TracePermanent link for this heading

Following variables define trace settings:

  • TRACE
    Path of the file where, when using the trace kernel, different information is logged.
  • TRACEMODE
    This mode serves to log activities of the Fabasoft Folio Kernel or to debug own software components.
    • Normal
      Important trace messages are displayed in a message box.
    • Silent
      There is no display of trace messages in a message box.
  • TRACEFLAGS
    The default trace flags used for all software components. The flags can be combined using a separator (e.g. space, comma, semicolon or pipe).
    • all: Enable all traces.
    • calls: Enable tracing of calls.
    • errors: Enable tracing of errors.
    • expressions: Enable tracing of expressions.
    • none: Disable all traces.
  • TRACEEXIT (TRUE/FALSE)
    The value of this variable determines whether trace messages should be displayed when closing the Fabasoft Folio Web Client or not.
  • TRACELOCK (TRUE/FALSE)
    If this variable is set, trace messages are displayed by the thread that is responsible for the management of locks.
  • TRACECACHE (TRUE/FALSE)
    This variable determines if the thread that is responsible for the management of the client cache displays trace messages.

Full-Text SearchPermanent link for this heading

Following variables define search settings:

  • INDEXCLIENTTIMEOUT
    The value of this variable determines the duration after which a “slow index object” or "slow index content" message will be written in the indexing logs while building the Fabasoft Mindbreeze Enterprise full-text index from Fabasoft Folio. The default value is 1000 ms.
  • INDEXSEARCHLIMIT
    The maximum number of objects, which are searched for while other indexing phases are running. By default, no limit is enforced.
  • INDEXSEARCHPRELOADLIMIT
    The maximum number of objects, which are searched for and loaded in the background (in case of INDEXLOADTHREADS=1) while other indexing phases are running. By default, 50 chunks are preloaded in the background. As preloading objects highly affects the memory usage, please consider limiting the kernel object cache size using the variable CACHESIZE.
  • INDEXLOADBYPASSCACHE
    If enabled, object loading does not affect the COO service cache. Newly loaded objects are not cached to prevent cache pollution that could influence the user experience on production systems.
  • INDEXLOADCOMPLETE
    If enabled (default), the objects are loaded using LoadAllAttributes. Otherwise the objects are loaded without the property COOSYSTEM@1.1:objversions.
  • INDEXLOADTHREADS
    The number of threads, which are used for loading the objects. Please consider the COO service load and worker threads when raising this value. By default, only one thread is used.
  • INDEXPRELOADLIMIT
    The maximum number of objects, which are loaded in the background while processing the current chunk. Its granularity is the chunk size divided by the number of load threads. By default, one chunk is preloaded in the background. As preloading objects highly affects the memory usage, please consider limiting the kernel object cache size using the variable CACHESIZE.
  • INDEXOBJECTPROCLIMIT
    The maximum number of objects, which are processed in the background while finalizing the current chunk (loading contents, sending data to Mindbreeze, and storing the index state). By default, one chunk is processed in the background. As increasing this limit highly affects the memory and disk usage, only do so if there is an indication that the default value causes excessive wait times for other indexing phases based on “execution statistics” provided after a successful indexing run.
  • INDEXSENDTHREADS
    The number of threads, which are used for loading contents and sending data to Mindbreeze. Please consider the Mindbreeze load and the desired number of concurrent connections to Mindbreeze when raising this value. By default, the indexing service thread count COOSYSTEM@1.1:idxsrvthreadcount is used.
  • INDEXSTATETHREADS
    The number of threads, which are used for storing the index state. Please consider the COO service load and worker threads when raising this value. By default, the indexing service thread count COOSYSTEM@1.1:idxsrvthreadcount is used. In case of an index state file, only one thread is used.
  • FTSACLCHECKALLROLES
    If enabled (default), object ACLs are indexed in a way that supports searching with all roles in case of the Mindbreeze web client. Consequently, specific optimizations cannot be performed (e.g. more precise access control entry indexing in case of content indexing with non-standard access types). If that client is not used, the option can be disabled to improve search performance.
  • FTSACLROLEUSERMEMBEROF
    If enabled (default), user groups (COOSYSTEM@1.1:usermemberof) are considered for determining the current user context for a search. Otherwise, user groups are ignored unless no roles are active (all clients) or all roles are active (Mindbreeze web client). Indexed object ACLs do not differentiate between groups referenced via COOSYSTEM@1.1:ACLGroupKind(ACLGROUP_ATTRIBUTE) (relevant for role access) or groups referenced in COOSYSTEM@1.1:ACLUserKind(ACLUSER_ATTRIBUTE) (relevant in general). Consequently, depending on the scenario, the user context might contain too many groups leading to too many ACL filter results. If COOSYSTEM@1.1:ACLUserKind(ACLUSER_ATTRIBUTE) group access is not relevant, the option can be disabled to improve performance.

ExpressionsPermanent link for this heading

Following variables define expression evaluation settings:

  • EXPRESSIONLOOPTIMEOUT
    The value of this variable determines the maximum duration of an expression loop  in case of secured expressions (evaluated with COOEF_SECURED).
    Default value: 10000 ms
  • EXPRESSIONLOOPASYNCTIMEOUT
    The value of this variable determines the maximum duration of an expression loop  executed in the context of COOSYSTEM@1.1:ExecAsync in case of secured expressions (evaluated with COOEF_SECURED).
    Default value: 60000 ms

Other SettingsPermanent link for this heading

Following variables define additional settings:

  • AUDITENTRYLIMIT
    The value of this variable determines the maximum number of entries in an audit log object.
    Default value: 2500 entries
  • AUDITSESSIONLIMIT
    The value of this variable determines the maximum number of open connections to the audit data source (per Fabasoft Folio Kernel instance).
    Default value: 0 (unlimited).
  • AUDITTIMEOUT
    When logging an action, the value of this variable determines the period of time after which a new entry concerning this action is generated in the audit log object.
    Default value: 60 s.
  • CACHEDDOMAIN (TRUE/FALSE)
    The value of this variable is TRUE by default, which means that the Fabasoft Folio Kernel connects to the domain which is stored in the CURRENTDOMAIN environment variable next time it is started.
    If this value of CACHEDDOMAIN is set to FALSE the value in the variable CURRENTDOMAIN is not considered.
  • CURRENTDOMAIN
    This variable contains the domain ID to which the Fabasoft Folio Kernel on this machine was connected last. A connection to this domain is established at the next start unless another setting is made (see the CACHEDDOMAIN variable).
  • EXECASYNCSHUTDOWNTIMEOUT
    The amount of time (in milliseconds) which should be waited for threads which are started using COOSYSTEM@1.1:ExecAsync before the process gets terminated.
    Default value: 10 000 ms.
  • HOMEDOMAIN
    Using this environment variable, it can be explicitly defined in which domain the user object should be searched for when logging in.
  • LASTLANGUAGE
    In this variable, the object address of the language object that was used by the last user of the Fabasoft product environment in his user environment is saved.
  • LASTMACADDRESS
    This variable stores the MAC address of the network card. This is required for the MLI mode.
  • MAXMETHODRECURSION
    Specifies the maximum number of possible recursions which can occur until an error message is displayed.
    Default value: 256
  • RELAXLOGIN (TRUE/FALSE) (not intended for production use)
    If the variable is set, CooRuntime::Login within a method is allowed for privileged users. Additionally, unprivileged users can fall back to the original user context. This feature intended for test systems is useful for executing app.ducx unit tests that require user switching.
    Note: Setting this variable disables essential security mechanisms. Therefore, it must not be used in production.
    Default value: false
  • SAFEMODE (TRUE/FALSE)
    If the value of the variable SAFEMODE is set to TRUE, only methods of the software components of the domain 1.1 and 1.1001 are executed. The SAFEMODE variable can only be executed when using the trace kernel.
  • SIMPLELOGIN (TRUE/FALSE)
    The identification of users when logging in to the Fabasoft product environment works with different methods. If SIMPLELOGIN is set to TRUE, only the Microsoft Windows account is considered.
    This variable is also set to TRUE when calling a Fabasoft Folio Web Service. The method used to modify the values of variables is SetKernelFlags().
  • STAT
    Path of the file where using appropriate software statistics data can be logged.
  • STATFLAGS (Microsoft Windows Registry)
    -statflags (command line)
    In the Fabasoft Folio Kernel, statistics about all objects which are accessed are created. Via the environment variable STATFLAGS, the different statistics can be displayed. The value can be declared in decimal or hexadecimal forms.
    • -statflags = 0
      Disables the statistics functionality
    • -statflags = -1 or 0xFFFFFFF
      Enables the statistics functionality

Variables which are set via STATFLAGS:

  • STAT_OBJECT
    Object-related statistics
    0x00000001
  • STAT_ATTRIBUTEDEFINITION
    Attribute-related statistics
    0x00000002
  • STAT_ACTION
    Action-related statistics
    0x00000004
  • STAT_ERRORMESSAGE
    Error message-related statistics
    0x00000008
  • STAT_GENERAL
    General statistics
    0x00000010
  • STAT_TRANSACTION
    Transaction-related statistics
    0x00000020
  • STAT_REFRESH
    Statistics of the refreshes
    0x00000040
  • STAT_LOAD
    Statistics of the loads
    0x00000080
  • STAT_METHOD
    Statistics of the method calls
    0x00000100
  • STAT_KERNEL
    Statistics of the kernel calls
    0x00000200
  • STAT_TOP
    Additional display of the top 20 entries of statistics values
    0x10000000
  • STAT_DETAILED
    Additional display of all entries of statistics values
    0x20000000
  • STAT_NONE
    Disables the statistics functionality
    0x00000000
  • STAT_ALL
    Enables the statistics functionality
    0xFFFFFFFF

By default, all settings except STAT_OBJECT are active.

Example:
STATFLAGS=264 or STATFLAGS=0x00000108 displays statistics concerning method calls and error messages.

Download PDF

Download PDF