- 5 minutes to read

Getting started

The Getting started user guides are intended for end-users of Nodinite typically using the Web Application we call the Web Client. On these pages we provide simplified information to give you the big picture with links to other parts of the more technical in depth documentation where needed.

Regardless of the solution/engine/technology being used to solve system integration needs we at Nodinite do our best to provide all stakeholders with relevant and up to date information. Nodinite has the following main features:

Monitoring Logging Repository
Get alerts whenever there is a problem and fix it before it gets someone else's problem too Find what you are looking for Documented solutions are key to personal independence

Order scenario

Learn how to get all the pieces together as a whole enabling self service for a fictive order flow.

# Blog post Description Logging Monitoring
1 Enabling self service for an Order flow <START HERE!> Overview and background for blog post series
2A Getting the data : Enable tracking using Microsoft BizTalk Server Learn how to fetch business transactions from the Microsoft BizTalk Server integration platform
2B Getting the data : Enable tracking using Azure Logic Apps Learn how to fetch business transactions from the Azure Cloud
2C Getting the data : ... Learn how to fetch business transactions from the ...
3A Find order by Order Id Learn how to extract the OrderId from transaction payload using a Search Field
3B Find order by Order Id using a Log View Learn how to enable self service to find order by order id using a Log View
3C Restricting access to Log Views Learn how to limit what users can see and do
3D Styling an order Learn how to visualize an order in a user-friendly format using stylesheets
4 Who has accessed order information Learn how to find out who has accessed potentially sensitive order information
5 Get alerts when orders stop coming Learn how to get alerts when you get to few orders
6 Get the insights using PowerBI Learn how to extract KPI's that is relevant for you

Logging

Find what you are looking for

How to use

The logged events with optional payloads (data) can be accessed using tailored Role based Log Views. All operations within Nodinite are audited.

End-user perspective Administrator perspective
How do I find order '123' that I'm missing How do I create a Log View where end-users can find orders by Order Id

What

Nodinite logs and archives events and data from many system integration platforms to provide true 'end-to-end logging' so you can find what you are looking for.

Why

System integration solutions are typically scattered over many systems on-premise and in the cloud. Even knowing which haystack to choose before even digging deeper can be a big challenge. With Nodinite you get access to all data you need in one single place without a plethora of other products with different learning curves and often hard to understand pricing models.

How

Nodinite uses depending on solution/integration broker either Logging agents or code that resides inside the the integration brokers/applications to emit events and data for Nodinite to fetch.

Developers start here

Monitoring

Get alerts whenever there is a problem and fix it before it gets someone else's problem too

How to use

Monitored Resources can be accessed and managed using tailored Role based Monitor Views. All operations within Nodinite are audited.

End-user perspective Administrator perspective
How do I know there's a problem with my Order integration? How do I create a Monitor View for the Order flow?

What

Nodinite monitors all the links as Resources in the system integration chain to provide true 'end-to-end monitoring' so you can get alerts whenever there is a problem and fix it before it gets someone else's problem too.

Why

System integration solutions are typically scattered over many systems on-premise and in the cloud. Even knowing which haystack to choose before even digging deeper can be a big challenge. With Nodinite you get access to interact with all monitored Resources in one single place without a plethora of other products with different learning curves and often hard to understand pricing models.

How

Nodinite uses Monitoring agents to supervise and interact with monitored Resources.

Repository Model

Documented solutions are key to personal independence

How to use

The documentation in Nodinite is a CMDB feature we call the Repository Model. The Repository Model is managed by a Nodinite Administrator/repository contributor and is used (do look at the Repository Model as being a reward) within:

Feature Description
Monitor Views The documentation is readily available only one click away and you do not need to spend time on searching
Alerts Get the information you need to resolve the matter right away or use it to create well defined tickets in your incident management tool
Log Views Easily find out what Integration logged events belong to
Knowledge base Articles From within Monitor Views you get instant access to related articles often with user guides containing information about how to resolve common problems
Integration Landscape An image says more than a thousand words. With Nodinite you can drag and drop entities (shapes) on a canvas creating an holistic overview for anyone to understand
End-user perspective Administrator perspective
How do I know how many Integrations I have? How do I create and manage Integrations?

What

Nodinite has a standard definition with common system integration entities. These entities are related and the end result is a representation that fits all integration platforms.

Why

System integration solutions are typically scattered over many systems on-premise and in the cloud. Even knowing which haystack to choose before even digging deeper can be a big challenge. With Nodinite you can document them all in one single place without a plethora of other products with different learning curves and often hard to understand pricing models.

How

Nodinite has built-in administration to manage the Repository Model. To automate the creation of documentation, developers can also populate and manage this data using the Web API part of their their DevOps routines.