- 5 minutes to read

Step 3: Infrastructure

This step covers the database and network plumbing that the installer needs: the SQL Server connection for the Configuration Database, the SQL deployment tooling, the SQL DB Lookup entries, and the outbound proxy.
Portal infrastructure step
Example of the Portal Infrastructure step in the Environment wizard.

Click the Infrastructure step button to review the database and network settings. The Portal writes these values into the generated installation package.

You can provide:

Understanding What the Installer Does with SQL Server

The installer creates or updates only the Configuration Database. It deploys the database schema with SqlPackage from DacFX, running as the user who runs the CLI. It creates no Log Database: the Logging Service creates the first Log Database when it starts for the first time, and every later one (Install Log Databases).

flowchart LR subgraph "Nodinite Portal: Step 3" P1["fa:fa-keyboard Connection string
entered in the Portal"] P2["fa:fa-toggle-on Provide during
install/update"] end subgraph "Step 7: CLI on the Core Services Server" ARG["fa:fa-terminal --database-connection-string,
environment variable, or prompt"] SQLP["fa:fa-gears SqlPackage.exe (DacFX)"] end subgraph "After the installation" LS["fa:fa-hard-drive Logging Service
first start"] end subgraph "SQL Server" CDB["fa:fa-database Configuration Database"] LDB["fa:fa-database First Log Database"] end P1 --> SQLP P2 --> ARG ARG --> SQLP SQLP -->|"Create or update"| CDB LS -.->|"Creates"| LDB style P1 fill:#2678BD,color:#fff style P2 fill:#2678BD,color:#fff style ARG fill:#E47528,color:#fff style SQLP fill:#E47528,color:#fff style LS fill:#3F827B,color:#fff style CDB fill:#93d16d style LDB fill:#FFD525

Diagram: the connection string comes from the Portal (blue) or from the CLI at run time (orange); SqlPackage from DacFX creates or updates the Configuration Database (green). Later, the Logging Service (teal) creates the first Log Database (yellow).

Configure SQL Server connectivity

Enter the information about the target SQL Server.
Database settings
Example of the SQL Server connectivity settings for the target SQL Server.

  • Database Type
  • Whether you provide the SQL connection string now or during install/update execution.
    Database prompt for connection string
    Example of the connection string prompt option, used when you provide the connection string during install/update execution.
  • The connection string for the target SQL Server.
  • The SqlPackage path from DacFX and any custom Dacpac locations.
  • Open Dashboard after install: opens the Web Client in the default browser after each install or update.

Choose one of these two paths

  1. Enter the SQL connection string directly in the Portal.
  2. Toggle the option to provide it during install/update execution. Then pass it with --database-connection-string or the NODINITE_DATABASE_CONNECTION_STRING environment variable, or answer the CLI prompt (Step 7: passing arguments).

Important

The connection string is mandatory. Provide it here or at run time by toggling the option; an undefined database connection is not supported.

For tested formats and security guidance, use the SQL Server Connection String examples. The user who runs the CLI needs sysadmin on the SQL Server instance during install and update (SQL Server Sysadmin Requirements).

Install options (SqlPackage and Dacpac tooling)

Review the install options in this step, including the SQL deployment tooling paths.

  • Confirm the SqlPackage.exe path. DacFX must be installed on the servers where the installer runs. The default path is C:\Program Files\Microsoft SQL Server\170\DAC\bin\SqlPackage.exe; check it with the DacFX verification.
  • Confirm the Dacpac-related paths when your setup uses custom package locations.
  • Keep these values aligned with the account that runs install and update.

Use SQL Server options for deployment-model specifics.

Configure SQL DB Lookup

💡 This is an optional configuration. Configure it only if you need the Nodinite sqllookup Formula plugin.

Use the SQL DB Lookup section when Search Field Expressions should query reference tables in SQL Server with the sqllookup Formula plugin.

SQL DB Lookup Section
Example of the SQL DB Lookup section with named connection string entries for Formula expressions.

Add a SQL DB Lookup entry

  1. Click + Add in the SQL DB Lookup section.
    SQL DB Lookup Add Button
    Example of the Add button that inserts a new SQL DB Lookup row in the Portal.
  2. Enter a Name. It becomes the CSTRID, the first parameter, in the sqllookup expression.
  3. Enter the Connection String for the reference database.
  4. Save the Environment after you add the entry.

SQL DB Lookup rules

  • Use a stable name, such as SqlDbLookupLocal or CustomerReferenceData.
  • Keep the connection string read-only from the target database's point of view.
  • Don't rename an SQL DB Lookup entry after Search Field Expressions start using it.
  • Use the same name in your sqllookup expressions.

Example mapping

With an SQL DB Lookup entry named mylookup, use that name in a Search Field Expression with the sqllookup Formula plugin:

sqllookup('mylookup', 'MyLookupDB', 'AreaCodes', 'Name', 'AreaCode', body)

For the full syntax and more examples, see the sqllookup page.

Configure Network / Proxy

💡 This is an optional configuration. Configure it only if your servers need an outbound HTTP proxy to reach external endpoints.

The Network / Proxy section controls how the installer reaches outbound HTTP endpoints during registration, health checks, and OAuth discovery calls. Define the proxy mode, the proxy URL, and the bypass hosts here.

Network / Proxy section with Proxy mode set to system, Proxy URL, the two proxy toggles, and Proxy bypass hosts (7.12)
The Network / Proxy section defines the proxy mode, URL, and bypass hosts used by the installer for outbound HTTP, health checks, and OAuth discovery calls.

Typical values to review

  • Proxy mode: Use Windows/system proxy (the default) uses the server's Windows proxy settings, No proxy disables proxy use, and Manual proxy routes through the proxy you enter in Proxy URL. The CLI proxy overrides use the same modes as system, none, and manual.

    Proxy mode list with Use Windows/system proxy, No proxy, and Manual proxy (7.12)
    The three proxy modes; Use Windows/system proxy is selected by default.

  • Proxy URL: the proxy, including scheme and port, for example http://proxy01:8080.

  • Use Windows credentials for proxy auth: the installer authenticates to the proxy as its own process identity.

  • Bypass local and intranet names: localhost and single-label internal server names skip the proxy.

  • Proxy bypass hosts: hosts the installer reaches directly, one host or wildcard per line, such as *.dev.local or sql01.contoso.local; commas and semicolons are accepted too.

To change the proxy only for one run, use the CLI proxy overrides. Which hosts the servers must reach is listed in the Network and Firewall Overview.

Next Steps