- 4 minutes to read

Step 3: Infrastructure

This step covers the database and environment plumbing that the installer needs before the package is generated. In the current Portal flow, the main responsibilities are the SQL Server configuration, the SQL DB Lookup entries, and the outbound proxy settings.
Portal infrastructure step
Example of the current Portal Infrastructure step in the environment wizard.

Click on the Infrastructure step button to review the database and network settings that the installer will use to prepare the environment. The Portal collects these values and writes them into the generated installation package.

You can provide information about:

Configure SQL Server connectivity

Configure information about target SQL Server: Database settings
Enter connectivity information about target SQL Server.

  • Database Type
    • SQL Server Standalone (default)
    • Always On Availability Group (AOAG)
    • Managed instance (Azure)
  • Decide whether to provide the SQL connection string now or during install/update execution. The Portal will use this value to generate the package and write it into the configuration file.
    Database prompt for connection string
    Example of the SQL Server connection string prompt that appears when the user chooses to provide it during install/update execution.
  • Connection string as required by the target SQL Server.
  • DACFX tooling paths for the SqlPackage.exe executable and any custom Dacpac locations.
  • Open Dashboard after install - Decision whether to open the Web Client after the installation is complete. The Portal uses this value to create the first user which ensures that you can sign in to the Web Client after the installation is complete.

On the current Infrastructure step, the user is expected to either provide the SQL Server connection string directly in the Portal or provide it during install/update execution.

Choose one of these two paths

  1. Enter the SQL connection string.
  2. Leave it for install/update and provide the connection string in the deployment command flow.

For tested formats and security guidance, use the SQL Server Connection String examples page.

Install options (SqlPackage and Dacpac tooling)

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

  • Confirm the SqlPackage.exe path for your SQL tooling installation. DACFX must be installed on target servers where the installer runs. The default path is C:\Program Files\Microsoft SQL Server\170\DAC\bin\SqlPackage.exe.
  • Confirm Dacpac-related paths when your setup uses custom package locations.
  • Keep these values aligned with the account that executes install/update.

Use SQL Server options for deployment-model specifics, and DacFX for SqlPackage tooling reference.

Configure SQL DB Lookup

💡This is an optional configuration. Only configure it IF you need the Nodinite sqllookup Formula plugin.

Use the SQL DB Lookup section when you want Search Field Expressions to query reference tables from 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.

  1. Enter a Name value. This becomes the CSTRID or first parameter in the sqllookup expression.
  2. Enter the Connection String value for the reference database.
  3. Save the Environment after the entry is added.

SQL DB Lookup rules

  • Use a stable name such as SqlDbLookupLocal or CustomerReferenceData.
  • Keep the connection string read-only from the perspective of the target database.
  • Do not rename an existing SQL DB Lookup entry after Search Field Expressions start using it.
  • Reuse the same name in the sqllookup Formula page and in your Search Field Expressions.

Example mapping

If you add a SQL DB Lookup entry named mylookup, you can later use that name in a Search Field Expression with the sqllookup Formula plugin.

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

For the full syntax, configuration notes, and examples, continue with the dedicated sqllookup documentation.

Configure Network / Proxy

💡 This is an optional configuration. Only configure it IF your environment requires outbound HTTP proxy settings to reach external endpoints.

The Network / Proxy section controls how the installer reaches outbound HTTP endpoints during registration and health checks. This is the place to define the proxy mode, proxy URL, and bypass hosts that the generated package should use.

Network / Proxy
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: Off, System, or explicit proxy configuration
  • Proxy URL: used when the environment requires an outbound HTTP proxy
  • Bypass list: hosts or domains that should be accessed directly without the proxy
  • Authentication for outbound connectivity where the network requires it

Next Step