How do I install a new instance of Nodinite - Part 2?
Info
This page is a continuation of 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.
Please review the steps of interest. Then, at least, you must add yourself or the account to use with the Nodinite Web Client in step 13.
Step 9 Configuration
Configure Log Database Options
Provide options that determine how large or old Log Databases can grow.
Split options by size or time
- Size to split database on in (GB) - Default is 31 GB, and modern SQL Server instances with outstanding 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 to store Log Events 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
On the Verify page, you will start the Logging- and Monitoring Service.
Step 15 Start Logging Service
If you are installing a new instance of Nodinite, the Logging Service creates a new Log Database on the first start. This behaviour is designed to validate and test that the account for the Logging Service has sufficient rights to create new Log Databases.
Important
If you are upgrading Nodinite with existing old Log Databases; You must ensure all old Log Databases are first updated before starting the Logging Service. Duplicate the tab in the browser, navigate to the installed environment, and manually execute the scripts to have all existing log databases updated.
Important
If you are using a named instance on a fail-over cluster, you must ensure that the linked server localhost\instance exists. You may need to manually deploy the log database if the Logging Service fails to create the first log database. Contact our technical support if the problem can't be resolved at this stage.
Click the 'Start' button to start the Logging Service
When and if the Logging Service starts, information about the online Log Database is present 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 the 'Start' button to start the Monitoring Service
Here's an 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. 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
Make sure to perform Hardening on the instance.
After the installation completes, make sure to assign access rights for end-users that you want to grant access to the Nodinite Web Client; review the Assign Access Rights user guide for details.
Make sure the appropriate SQL rights are set for future Nodinite Log Databases. The Logging Service depends on the following System Parameters:
You can perform additional tuning on the instance; review the System Parameters users guide for additional information on this matter.
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 the latest DaxFX package.
#2. Unauthorized
If end-users can't log on 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
Review the IIS Authentication settings troubleshooting guide if you encounter any other IIS-related problems.
Next Step
Administer Nodinite
Configure BizTalk LogAgent
Related
Download
Update
Web Client
Release Notes
Logging Service
Monitoring Service
Log Databases