How do I install a new instance of Nodinite - Part 2?
This page is a continuation from Part 1
In the following steps, you will configure the default behaviour for Nodinite. All these settings are System Parameters unique for each instance of Nodinite and can therefore easily be changed later.
Step 9 Configuration
Configure Log Database Options
Provide options that determine how large or how old Log Databases are allowed to grow.
Split options by size or time
- Size to split database on in (GB) - Default is 31 GB, and modern SQL Server instances with great DISK IO can manage 50-100 GB
- Days to split database on - Default is 10000 days which means that the database splits based on the size
Step 10 Configure Logging Options
Provide the options for how long time to store events and payload. These settings apply as the default setting for new Message Types.
Options for how long time to keep events and payload
- The default number of days to keep logged events
- The default number of days to keep data/body logged events
Step 11 Configure Monitoring Options
Provide the options for how long time to store monitoring events. This historical data is available in the Monitor Views graphs.
- The number of days to keep Monitoring Events - Default is 32; Our recommendation is at least 90 days for production environments.
Step 12 Configure Active Directory Support
Provide options for integration with Active Directory:
When checked; Enable the use of Windows Active Directory groups
- Enable role-based support for Active Directory Groups - Default = checked
Step 13 Configure Administrators
Provide options for what users are granted access to the Web Client as part of the Administrators Role.
Add the users to be Nodinite Administrators.
Step 14 Review Configuration
Review the configuration and click on the 'Next' button
Step 15 Start Logging Service
If you are installing a new instance of Nodinite, then a new Log Database is created by the Logging Service on the first start. This behaviour is by design to validate and test that the account for the Logging Service has sufficient rights to create new Log Databases.
Click on the 'Start' button to start the Logging Service
When and if the Logging Service starts, information about the online Log Database presents on the page. This is either a new one or your updated old existing one.
Basic information about online Log Database
Step 16 Start Monitoring Service
Your next step is to start the Monitoring Service.
Click on the 'Start' button to start the Monitoring Service
Example of the successful start operation of the Nodinite Monitoring Service
Step 17 Finish
Congratulations! you have now successfully installed Nodinite!
You should now be returned to the page managing the environment. From here you can click on the 'Web Client' button to quickly navigate further in a new tab to the Web Client.
Open the Nodinite Web Client quick link button
Step 18 Post installation steps
After the installation is completed, make sure to assign access right, review Assign Access Rights user guide.
Also make sure the appropriate SQL rights were set for future Nodinite Log Databases. The Logging Service depends on the following System Parameters:
Additional tuning can be performed, review the System Parameters users guide for additional information.
Install Logging Agents
To enable Logging please review the Installing and Configuring Nodinite Log Agents user guide.
Install Monitoring Agents
To enable Monitoring please review the Installing and Configuring Nodinite Monitoring Agents user guide.
Common errors
Each input field during the installation steps must be clicked on to validate content. If you do not click on each input field, the validation process will not be performed and the installation can not continue.
#1. Missing SQL package
The file SqlPackage.exe
was not found on the server 'localhost':
Solution Download and install the following file from here
DACFramework.msi
(18.0 or later to match your version of SQL Server, higher versions are backwards compatible)
#2. Unauthorized
If end-users can't logon to either the Web Client or the Web API although they are registered as either Users or Windows AD Groups, make sure the end-users have the local policy: "Access this computer from the network" set
default settings example for Windows 2016
#3. IIS Authentication settings
If you encounter any other IIS related problems, make sure to review the IIS Authentication settings troubleshooting guide.
Next Step
Administer Nodinite
Configure BizTalk LogAgent
Related
Download
Update
Web Client
Release Notes
Logging Service
Monitoring Service
Log Databases