With xSuite Interface, you can distinguish between multiple tenants within one program instance. When worker instances are defined, processing scenarios are assigned to tenants within the global configuration. For information about the concrete configuration properties, see Workers.

The scenarios to be processed by this instance are linked to each worker instance. In the process of configuration, the tenant within which the worker instance is to be executed needs to be defined. You can specify any tenant name. There is no general declaration of existing tenants at a higher point in the hierarchy.

You can thus apply the scenario configuration to multiple tenants by assigning the same scenario configuration to different tenant-specific worker instances. If individual properties within the scenario configuration have tenant-specific value specifications (e.g., different file paths for input data and output data), you can set these values dynamically for specific tenants via Constants.

By specifying different tenant names, the program implicitly creates separate resources (i.e., separate administrative databases). The administrative databases are created on the same database server, since this is defined globally. If a file system is used for temporary file storage, separate storage folders are also created. The globally defined database name is automatically given a name suffix for this purpose. The storage folder is given a subfolder corresponding to the name of the tenant. This naming logic is also applied when using single-tenant systems. If a tenant name is not explicitly defined for the tenant, the default name "Default" will be used.

Logging to the file system and to a database is handled differently. In a multi-tenant configuration, global log entries that are not tenant-specific are written to a separate log file or database with the name suffix "Global." If only one tenant is configured, such entries are output to the same log resource as the specific entries for the tenant are.

If no worker instance is active, meaning that no tenant is defined, then the global log resource will also be used. The exception to the rule is that the tenants that are to be displayed by this web service can be defined in the properties of the status web service. If the web service is active and exactly one tenant is specified here, this tenant will be used as the target for database logging.

A database with the suffix Global in its name is also used to save configuration data. The prerequisite for this is that database-based storage of the configuration data is activated and takes place in the internal administrative database.