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.
A simplified example of 2 systems where System A passes information to system B
Some examples of a System:
- BizTalk
- SAP
- TEIS
- Dynamics 365
- Insightly
- PIM
- MES
- Customer ABC
- HR+
- Bluegarden
- Evatic
- Basware
- ...
You can easily manage relations between Systems using the Nodinite Integration Landscape feature
Interactions between the systems may be more complex than just System A to System B:
A more complex systems integrations scenario involving multiple Systems
A System has a unique name within Nodinite and can contain arbitrary information/properties (Custom Metadata). One System has a connection with other Systems using the Nodinite concept of Services and the optional feature Contracts. Manage the relations using the Integrations entity. Using the Nodinite Web Client, Users can directly review what other Integrations relate to this particular System. If you would like to replace a System, you need to know the impact and what Integrations need rebuilding. This will have an immediate impact on the cost of replacing the System
The netlist of Integrations where this System is in use
Custom Metadata
As all entities of the Nodinite Repository Model, a System can have any number of Custom Metadata 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