- 3 minutes to read

Manage Integrations

An Integration is the root object in the 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-sitemap Integration) roService(fal:fa-cog 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 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

Quick facts for an Integration:

  • An Integration has a unique name
  • There can be any number of Integrations defined
  • Organize your Integrations using an unlimited number of Custom Metadata tags and Custom Fields
  • Integrations can be associated with an unlimited number of Monitor Views
  • Integrations can be associated from Log Events helping you form and visualize your message flows
    • A well defined Integration makes it super simple to apply relevant filters on Log Views
  • There can be any number of Services associated with an Integration
    • Services can be shared between Integrations
  • The Repository is meant to be rewarding and the more you invest, the more you will be rewarded

The defined relations are easy to access using the Actions button featured in the Integrations Overview:

View Relations
Animated example with easy access to the defined relations.

Manage Integrations

You can work with Integrations using the Nodinite Web Client. Use the following user guides working with Integrations:

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.

View Integration

From the Integration Landscape and the Integrations Overview, the end-user can click on a button to view the result:
View Integration
Example of a populated Integration.