Skip to content
LEF LEF Docs
GitHubLinkedIn

Installation (FAQ)

Installation FAQ

Section titled “Installation FAQ”

Database

Section titled “Database”

Is this a clean database installation?

Section titled “Is this a clean database installation?”

Yes. Start from a clean SQL Server installation.

Do you require a specific database name?

Section titled “Do you require a specific database name?”

No. Follow your organization’s naming convention.

What collation is required?

Section titled “What collation is required?”

Use Latin1_General_* (confirm the exact variant during setup). If a project requires a specific collation, document it in the project’s environment notes.

Which SQL users are required?

Section titled “Which SQL users are required?”

We typically need two SQL logins:

  • Installer/admin login (sysadmin): used for initial installation and upgrades.
  • Service login (least privilege): used by the application runtime so end users do not need direct database access.

Does the database need to be on a specific disk?

Section titled “Does the database need to be on a specific disk?”

No strict requirement. For large ERP-style deployments, disk layout can matter for performance; decide per environment.

Windows environment preparation

Section titled “Windows environment preparation”

Preparation

Section titled “Preparation”
  • Define URLs for test and production (e.g. app-test.example.com and app.example.com).
  • Provision a Windows Server for the application tier (sizing depends on the solution).
  • Install SQL Server 2022 (if SQL is hosted on Windows for this environment).
  • Get the required installation packages (internal distribution location).
  • Install and configure IIS per Thinkwise docs:
    • Enable .NET Framework features
    • Enable performance features
    • Enable WebSocket

LEF installation session (high level)

Section titled “LEF installation session (high level)”

The typical install sequence is:

  1. IAM (use the installer/admin SQL login)
  2. GUI deployment
  3. Indicium setup

For Indicium/IIS:

  • Create a dedicated IIS Application Pool.
  • Run the pool under the service account used by the application.

TLS certificate

Section titled “TLS certificate”
  • Provide an SSL certificate for the environment’s domain.
  • For internal environments, use the LEF Root CA (manual issuance) and/or AD CS for Windows servers (see LEF Root CA).

Environment notes (capture per project)

Section titled “Environment notes (capture per project)”

Capture these facts on the relevant environment definition page (don’t keep one-off notes here):

  • SQL Server hostname/FQDN (or *.db.lef endpoint when applicable)
  • SQL instance (if applicable)
  • Database name(s)
  • Runtime host/location
  • Public GUI hostname(s) and DTAP stage