- 2 minutes to read

What is a System?

Get started now: How to Add or Manage System user guide

A System is either the Source or the Destination entity for a message exchange for an Integration. Further, a Service (or Contract) belongs to a specific System in the Repository Model.

graph LR A(System A) -->|Interacts| B(System B)

A simplified example of 2 systems where System A passes information to system B

Some examples of a System:

  • BizTalk
  • SAP
  • Dynamics 365
  • Insightly
  • PIM
  • MES
  • Customer ABC
  • HR
  • Bluegarden
  • Evatic
  • Basware
  • ...

A System has a unique name within Nodinite and can contain arbitrary information/properties (Custom Meta Data). One system has a connection with other systems using the Nodinite concept of Services. These relations are managed from the Integrations entity. From the Nodinite Web Client, [Users][] can directly review what other Integrations have a relation with this particular system. If you would like to replace a System, then you need to know the impact, and what Integrations that need to be rebuilt. This will have an immediate impact on the cost of replacing the system

Relations The net list of Integrations where this System is being used

Custom Meta Data

As all entities of the Nodinite Repository Model a System can have any number of Custom Meta Data fields assigned.

Custom Fields

As all entities of the Nodinite Repository Model a System can have any number of Custom Fields assigned.

Next Step

System Overview
Add or manage System

Repository Model
Integrations
Services