- 2 minutes to read

Update the Nodinite Web API

The Nodinite Web API ships with the Core Services package, so you update it together with the Web Client, the Log API, and the other Core Services. You don't update the Web API on its own. The complete procedure is in Updating Nodinite v7; this page lists what matters for the Web API.

How the Update Works

  1. Select your environment in the Nodinite Portal (Step 1: Select Environment).
  2. Download and extract the ZIP for the Core Services (Step 2: Download/Extract ZIP).
  3. Run the CLI workflow in an elevated PowerShell 7 prompt: validate, dry-run, deploy (Step 3: Run the CLI workflow).

The CLI replaces the Web API binaries in its IIS web site and keeps the port, TLS binding, identity, authentication mode, and OAuth audiences from the Portal. To change any of these, change the value in the Portal (see What you set for the Web API in the Portal) before you download the ZIP. System Parameters are stored in the Configuration Database and stay as they are.

Tip

Test the update in a non-production environment first. Scripts and pipelines that call the Web API keep working with the same base URL, because the port and host name don't change.

Verify the Web API After the Update

  1. Browse to Scalar on the Web API site, for example https://nodinite.contoso.com:<port>/scalar. If it opens, the Web API site is running.
  2. Send a test request to GET api/Users/whoami. The Collection.Version value in the response shows the installed Nodinite version.
  3. Open the Web Client and a Log View to confirm that the Web Client reaches the Web API.

If the CLI reports locked files, run iisreset and rerun the command; see File Locks Detected.

Note

Nodinite v6 is no longer supported. To move an existing v6 installation, follow Updating from v6 to v7.

Next Steps