Last updated: 2019-03-22

Plan your Installation

Eager to get started? Install Nodinite

On this page you will find valuable information that can help you get the best experience with our support and maintenance tool for system integration solutions we call Nodinite

Where do I find the latest information?

Access the latest information for Nodinite including system requirements and product support information from our Documentation page and from our Support page. These links are easy to access and are available for all users from within the self service web based interface we call Web Client.

Nodinite Release Notes

Review the prerequisites?

Nodinite is a platform from ground up designed for enterprise scalability with many different services and dependencies. Each of these prerequisite pages are documented in the Getting started folder structure. Depending on your needs and demands (and wallet) there will be different prerequisites for different target environments.

Windows SQL Firewall
Web Client
Web API
Log API
Logging Service
Monitoring Service
Configuration Database
Log Databases

Use the table above as your checklist to install and troubleshoot Nodinite

graph LR subgraph SQL Server roConfigDatabase(fal:fa-database Configuration database) --- |Linked Server| roLogDatabase(fal:fa-database fal:fa-database fal:fa-database Log databases) end subgraph Application Server roLogAPI(fal:fa-cloud-download Log API) --- roConfigDatabase roWebClient(fal:fa-globe Web Client) ---roWebAPI(fal:fa-cloud-sun Web API) roWebAPI --- roConfigDatabase roLoggingService(fal:fa-hdd Logging Service) --- roWebAPI roLoggingService --- roConfigDatabase roMonitoringService(fal:fa-watch-fitness Monitoring Service) --- roConfigDatabase roMonitoringService --- roWebAPI end

Architectural overview of the Core Services of Nodinite, customers with Logging typically have large amounts of data and run SQL Server on dedicated servers

Understanding your data and message processing requirements

It is important to be clear about your processing requirements, and to understand what you want Nodinite to do for you and your business. With Nodinite your business gets a self service tool where they can manage Logging and Monitoring all the way from specific business critical workflows to technical nitty gritty details, all according to your well defined policy. Nodinite has role based security.

About Your run-time Environment

When you start to plan your Nodinite environment, you must first consider the design of your system infrastructure, on-premise and/or in the cloud and you must at least understand that moving data around in your network allocates additional resources and costs. Nodinite is a software product that needs to be updated from time to time.

  • What volumes per day do you intend to log and process?
  • What volumes do you intend to keep? 1 million qualified business transactions per day is worth roughly 1 GB of compressed disk storage
    • What about GDPR - Nodinite Repository Model can help you keep track of what's important and what's not
  • Who should get the Alerts Nodinite transmits?
  • What and when? Build your knowledge base with Nodinite
  • Plan, design, order and implement the infrastructure required The capability and capacity provided by Nodinite vary according to the given processing power in which your system integration nodes are running
  • Plan, design, order and implement Service Accounts required by Nodinite and satellite systems to Log and Monitor
    • Who should be granted access to Nodinite and what should they be allowed to do?
      • Administrator
      • Contributor
      • Self service enabled users, read and download messages, repair and resubmit messages, view state of Monitored Resources, perform remote actions like start and stop services, ...
  • Plan, design, order and implement Installation of Nodinite and related Log- and Monitoring Agents
  • How, when and who updates Nodinite?
  • Plan, design, order and implement (make sure) backups are taken, remember Nodinite can run in a distributed environment with services scattered on-premise and in the cloud.
  • Who is (will be) the System Owner responsible for your Nodinite environment over time after it has been implemented?
    • The product key usually needs to be updated twice a year, before you leave for summer vacation and after you come back after the christmas holiday
  • Nodinite is a product that we constantly develop and invest in. Make sure to plan and allocate time and costs (time is money) for attending webinars, self-studies and tests, POCs and other occasions where we and/or our Partners present new information at various meet ups.
  • Subscribe to our newsletters and releases using our Support Portal

Buying Licenses for Nodinite

Nodinite enables our partners to offer Managed Services and you can feel free to contact one of our existing Partners or contact us at business@nodinite.com for guidance and recommendations.

If you want to become a partner, contact us at contact@nodinite.com or visit out Become a Partner page.

Recommendations

Nodinite should be installed on dedicated virtual machines on-premise or in the cloud with the databases co-located with existing database services. Make sure to assign new logical disks to your SQL Server instances hosting

You do not want extensive logging to block/inhibit your business critical solutions running on shared services.

  • CPU - At least 2 cpu:s or cores (x64) (multiple CPU's and cores are utilized due to extensive use of threads within Nodinite). Additional CPU/Cores does not affect the licensing for Nodinite.

Note: BizTalk, SQL etc. may require additional licenses depending on setup and license types used.

  • RAM - RAM >= 16 GB RAM on servers running any of the Core services

  • DISK - Nodinite should be installed on machines with dedicated Windows swap volumes (>2,5physical RAM) and SQL disks should have > 300 MB/S R/W. There should be a secured highly available backup volume (or network share) available with sufficient free space for Log Databases.

    • Make sure to have enough storage to keep old backups. If you have for example 3 historical large Log databases (~60GB) and you keep these backups for lets say 3 days, then you will need at least (3 * 60 * 3 = 540 GB Volume)
    • SQL Server: Typical Nodinite installations requires 30GB / Month. Normally data is erased after 14 days. If data is and or should be preserved additional disc space is required. This has to be carefully monitored by IT operations. Part of planned maintenance actions is to deal with historical data. This affects mainly disc usage. Large IMLog* databases will affect performance. Nodinite has support to store infinite (only restricted by disc space) amounts of data, but this function should depend on the use of multiple Log Databases. The recommendation is to keep each IMLog database < 50 GB. If possible the initial volume size should be 50GB and must (again) be carefully monitored by IT operations. All Nodinite Databases are on initial setup today configured in simple recovery mode. This is today by design but may change over time. It is supported to have Log* Databases in full recovery mode, but this will affect log disc space use until the next backup.

    We currently do NOT recommend using SQL Server Always On Availability Groups even though it is technically achievable

    If you intend to use SQL Server Always on Availability Groups then make sure to read the About SQL Server Always On Availability Groups user guide
  • Windows Event Logs - Nodinite Core Services, Log Agents and Monitoring Agents logs to the local event log as a last resort and might periodically write many records. Make sure that event logs on all servers with any of the Nodinite components are set to overwrite

Do not use fixed sized event logs

Training

You can buy training from our certified Partners or contact us att business@nodinite.com for guidance and recommendations.


Next Step

Prerequisites for the Install and Update Tool
How to download the latest version of Nodinite

Install Nodinite
Update Nodinite