- 3 minutes to read

Integration

An Integration is the root object in the Nodinite Repository Model (Documentation model in Nodinite) and keeps track of the relationship between included entities. A Nodinite Integration instance is meant to be designed before you create the solution making sure you can:

  • Share and communicate your proposed solution (design first)
  • Make sure you see and include all dependencies
  • Manage your service portfolio and plan and prioritize based on facts
  • Helps you get system integration solutions implemented based on formal and informal demands that your enterprise/solution architects (or other professional thinkers) may have instituted
graph LR subgraph "Repository" roi(fal:fa-puzzle-piece Integration) roService(fal:fa-gear Service) roSystem(fal:fa-dice-d6 System) roTCS(fal:fa-dot-circle TransportContracts) roMessageType(fal:fa-file MessageTypes) roEndpoint(fal:fa-sign-in Endpoints) roi -.->|0..*| roService roService --> |1..1| roSystem roService -.->|0..*| roTCS roTCS -.-> |0..*| roMessageType roTCS-.-> |0..*| roEndpoint end

The graphical representation that we call Integration Landscape is based on the relationship between the different Nodinite Repository Model artifacts.

Core Services Web Client User Guide Add or Manage
Integrations Integrations Overview Add or manage Integration
Systems System Overview Add or manage System
Services Service Overview Add or manage Service
Endpoints Endpoints Overview Add or manage Endpoint
Transport Contracts
Message Types Message Type Overview Add or manage Message Types
Custom Fields Custom Fields Overview Add or manage Custom Field
Custom Metadata Custom Metadata Overview Add or manage Custom Metadata
Articles Articles Overview Add or manage Article

Here's some quick facts about the Nodinite Integration repository item:

An Integration has a unique name.
There can be any number of (unique) Integrations.
Organize your Integrations using an unlimited number of Custom Metadatas and Custom Fields.
Integrations can be associated with Monitor Views.
You can access the Integrations data from within Log Views.
A well defined Integration makes it super simple to apply relevant filters on Log Views.
You can associate Systems containing Services and Contracts.

The reward is instant and grows the more you invest in the Repository!

Use the Actions button featured in the Integrations Overview to quickly access related entities:
View Relations
Here's an animated example showing the quick access to relations to other parts of the Nodinite Repository.

Manage Integrations

You can learn more how to work with Integrations using the Nodinite Web Client user guide in the Core Services section. Use the other following user guides working with Integrations:

Custom Metadata

As all entities of the Nodinite Repository Model, an Integration can have any number of Custom Metadatas.

Custom Fields

As all entities of the Nodinite Repository Model, an Integration can have any number of Custom Fields.

View Integration

From the Integration Landscape and the Integrations Overview, the end-user can click on a button to view the result:
View Integration
Here's an example example of the result from a populated Integration.