Step 1: Register Environment
Register your Nodinite environment in the Portal to begin the migration process.
Prerequisites
- Portal account with access to your Customer
- Valid Nodinite 7 product key
- Environment details (name, TCP ports for use in IIS, service accounts, database server and database name, etc.)
Steps
- Navigate to the Nodinite Portal
- Navigate to your Customer entry
- Ensure you have a Nodinite 7 product key:
- If missing, click Create Product Key
- Contact your Partner or Nodinite Support if needed
- Click the Environment tab
Example of the Environments tab showing registered environments in the Portal.
- Click Add Environment
Example of the Add Environment button in the Portal.
- Click Upgrade from Nodinite 6
Example of the Upgrade from Nodinite 6 button in the environment creation wizard.
Configure Nodinite 7 Variables
Set required variables for your environment. Configuration values are difficult to change later—they're embedded in app pools, folders, and databases.
Example of the Environment Name configuration screen in the Portal.
Basic Settings
| Variable | Default | Description |
|---|---|---|
| Environment Name* | Name of target environment NOTE: Reuse your v6 environment name | |
| Description | Purpose or usage description | |
| Destination Root Path | C:\Program Files\Nodinite |
Installation directory |
| Default Domain Name | <DomainName> |
Windows Active Directory Domain |
| Admin Account | <NodiniteAdminUserAccountName> |
Administrator account name |
| Admin Account Email | Administrator email (optional) |
Example of Installation Settings showing Destination Root Path configuration.
Example of Admin Account configuration.
Service Accounts
| Variable | Default | Description |
|---|---|---|
| Default Service Account Name | <DefaultServiceAccountName> |
Default services account |
Example of Service Accounts configuration showing default service account settings.
Ports
| Variable | Default | Description |
|---|---|---|
| Web Client Port | 40000 | IIS Port for Web Client NOTE: TLS/port 443 configured separately in Step 11 |
| Web API Port | 40001 | IIS Port for Web API |
| Log API Port | 40002 | IIS Port for Log API |
| Logging Service Port | 40003 | IIS Port for Logging Service |
| Monitoring Service Port | 40004 | IIS Port for Monitoring Service |
| Use Preview | Unchecked | Use preview version |
Example of Ports configuration showing default IIS port assignments for all services.
Configure Database Settings
Choose your database configuration:
- Standalone – Single SQL Server instance (Standard, Enterprise, Express, failover clusters)
- Always on – SQL Server Always On Availability Group
- Azure - Managed Instance – Azure SQL Managed Instance
- Edit Connection String Manually – Custom configuration
Example of Database Settings configuration with standalone SQL Server.
| Variable | Default | Description |
|---|---|---|
| Database Type | Standalone | Type of database configuration |
| Database Server Name | localhost |
SQL Server instance (use ServerName\InstanceName for named instances) |
| Database Name | NodiniteConfig_<EnvironmentName> |
Existing v6 database NOTE: Will be renamed to Nodinite_<EnvironmentName>_Config |
| Edit Connection String Manually | No | Manual connection string editing |
| Connect without encrypt | Checked | Connect without encryption |
| Encrypt Connection | Yes | Encrypt the connection |
| Trust Server Certificate | Checked | Trust server certificate |
| Sql Package Path | C:\Program Files\Microsoft SQL Server\170\DAC\bin\SqlPackage.exe | Path to SqlPackage.exe NOTE: DacFX must be installed (see Prerequisites) |
Note
For advanced scenarios, you can enable Edit Connection String Manually to provide a custom connection string with specific parameters.
For detailed information about connection string options including certificate validation, encryption settings, Always On Availability Groups, and troubleshooting, see SQL Server Connection Strings.
Example of Database Settings with manual connection string editing enabled when the Edit Connection String Manually checkbox is checked.
SQL DB Lookup
Configure named connection strings for the sqllookup Formula Plugin. Each entry you add here becomes available for use in Search Field Expressions to enrich log queries with reference data from SQL databases.
Example of SQL DB Lookup configuration showing named connection string entries.
Click + Add to create new connection string entries. Each entry requires:
- Name – Connection string identifier used in sqllookup expressions (e.g.,
SqlDbLookupLocal) - Connection String – SQL Server connection string for the reference database
Tip
The connection string names you configure here are used as the first parameter in sqllookup expressions. For example, adding a connection named
SqlDbLookupLocalallows you to use:sqllookup('SqlDbLookupLocal', 'DatabaseName', 'TableName', ...)
Completion Checklist
- Environment registered in Portal
- Product key verified
- All required variables configured
- Database settings configured
- SQL DB Lookup connection strings configured (optional)
- Configuration reviewed for accuracy
Once all required fields are completed, the Save and Next buttons will be enabled:
Example showing Save and Next buttons enabled when all required configuration is complete.
Warning
If the Next button remains disabled, review all required fields (marked with *) to ensure they are completed.
Example showing Next button disabled when required configuration is incomplete.
Next Step
Troubleshooting
Cannot Create Product Key
Problem: "Create Product Key" button is disabled or missing.
Solution:
- Verify you have a valid Nodinite 7 contract
- Contact your Partner for contract activation
- Email Nodinite Support
Save Button Disabled
Problem: Cannot click Save button.
Solution:
- Check for validation errors (red text) in form fields
- Ensure all required fields (marked with *) are filled
- Verify product key is valid
Validation Errors
Problem: Portal shows validation errors after clicking Save.
Solution:
- Environment Name: Cannot contain special characters
- Ports: Must be unique and between 1-65535
- Database Server: Must be accessible from Portal
- Service Accounts: Verify format (Domain\Username)
Database Name Already Exists
Problem: Portal shows database name conflict.
Solution:
- Verify you're using the correct v6 database name
- Check SQL Server for existing databases
- Ensure you haven't already migrated this environment