Database Settings¶

Database Settings configures the three storage categories used by Emakin: relational SQL databases, file repositories, and XML repositories.

The tab is divided into System Connections and Repositories. Use the first for the application system and archive databases; use the second for data, XML, and file repositories.

Use this page during installation and when you need to change how Emakin stores operational, archive, file, or XML data.

Environment Variable References¶

Sensitive connection values can be stored by using environment-variable placeholders instead of writing secrets directly into Host Administration fields.

Supported syntax:

1

${ENV_NAME}

Supported usage patterns:

1
2

${DB_CONNECTION_STRING}
Server=db;Database=mydb;User Id=admin;Password=${DB_PASSWORD};

Notes:

• placeholder resolution is applied at runtime and during Test Connection
• the raw ${...} text remains stored in Host Administration configuration
• if a referenced environment variable is missing, validation or runtime startup fails with an explicit error
• environment variable names must use letters, digits, and _; names containing . or - are not supported

System Connections¶

System Connection¶

The system connection stores the application’s system tables.

Use Test Connection to verify connectivity before startup.

The connection definition contains a Database Adapter, Name, and Connection String. Select the adapter that matches the target database, then use the connection string supported by that provider.

Replicate Fulltext Database to System Database¶

Full-text content is stored in the local file system of the agent machine and can also be replicated into SQL storage for synchronization with other agents.

In large deployments, this synchronization may reduce performance. Use a central file-system location with replication disabled when the full-text database becomes very large.

Archive Connection¶

The archive connection is used for archived records. Older data can be moved into this storage when a larger but slower archive area is preferred.

Like the system connection, it has an adapter, name, connection string, and Test Connection action.

Repositories¶

Repository Connections¶

At least one repository connection is required for normal application behavior. Repository databases store domain tables, and multiple repositories can be created.

Tenant-related data is sharded across repositories.

Use Test Connection to verify connectivity.

Each entry contains a database adapter, name, and connection string.

File Repositories¶

File repositories store uploaded files outside SQL storage.

Use them when file size growth would otherwise affect SQL performance.

File repositories support these providers:

• Local Directory stores files in a local or shared filesystem path.
• Google Cloud Storage stores files in a Google Cloud Storage service configured under Integrated Services.

Each repository defines the following settings:

File repositories are optional, multiple repositories can be configured, and files are replicated across all enabled repositories. When a new repository is enabled, existing files are queued for replication to it.

The Get Status button reports the total file, queued, and replicated counts for the repository.

XML Repository Connection¶

XML repositories store domain and process-related XML data.

Connection-string fields in this page also support the environment-variable placeholder format described above.

Specify its name and connection string before saving the host configuration.

Related Pages¶

• Data Stores
• Platform Services