- 6 minutes to read

Unlocking Integration Success with the Nodinite Repository Model

The Nodinite Repository Model is your central hub for documenting, visualizing, and managing system integrations and business workflows. This guide will help you:

  • ✅ Centralize and standardize integration documentation
  • ✅ Visualize your integration landscape for better decision-making
  • ✅ Enable fast access to actionable data for all stakeholders
  • ✅ Enhance compliance and governance with CMDB features

Create documentation that drives action and clarity!

From the Repository menu to Integrations filtered on Contoso, the Integration INT1001: Contoso Orders to ERP with its Services card open, and a click on the Service name Contoso ERP Order Intake that opens the Service's view page, animated walkthrough (7.12)
Animated walkthrough: open Repository > Integrations, filter on Contoso, open INT1001: Contoso Orders to ERP, expand its Services card, and click the Service's name to open its own page.

To find your way around the Repository:

  1. Open Repository in the main menu and pick a list, for example Integrations.
  2. Type in the filter box to narrow the list, and click a name to open the item's view page.
  3. On the view page, expand a card (for example Services or Systems) and click an item's name to open that item's own view page. Edit on the card opens the item's edit page in a new tab.

With the Nodinite Repository Model, you can:

  • Document integrations and workflows before you code
  • Visualize relationships and dependencies using Mermaid diagrams
  • Leverage pre-defined properties for consistency
  • Use Mapify Maps to build report-centric saved views for recurring analysis
  • Open View Modes for exact current relations using Mapify Rendering (interactive) or Mermaid Rendering (static)

Mapify Maps vs View Modes

When users ask for "Mapify," they often mean two different things:

Option What it does Typical usage
Saved Views (Mapify Maps) Stores user-defined report filters and layout choices Build reusable analysis views with grouped filters (AND/OR)
Mapify Rendering Interactive relation graph modal Drill into exact current relations with pan and zoom
Mermaid Rendering Static relation diagram modal Read and export the same exact current relations

Mapify Rendering and Mermaid Rendering use the same backend and show the same relation truth for the selected entity.

Repository Model Overview (Mermaid)

Below is a visual representation of the Repository Model and its key artifacts. This diagram helps you quickly understand how systems, integrations, services, endpoints, and metadata relate to each other.

graph TD subgraph "Business Layer" Systems[" Systems<br/>External applications"] Integrations[" Integrations<br/>Business processes"] end subgraph "Technical Layer" Services[" Services<br/>Integration components"] Endpoints[" Endpoints<br/>Communication channels"] MessageTypes[" Message Types<br/>Data formats"] end subgraph "Documentation & Metadata" Articles[" Articles<br/>Knowledge base"] Tags["fa:fa-hashtag Tags<br/>Classification"] CustomFields[" Custom Fields<br/>Extra properties"] CustomMetadata[" Custom Metadata<br/>Business context"] end Systems -->|"participates in"| Integrations Integrations -->|"implemented by"| Services Services -->|"exposes"| Endpoints Endpoints -->|"handles"| MessageTypes Integrations -->|"documented in"| Articles Integrations -->|"tagged with"| Tags Integrations -->|"extended by"| CustomFields Integrations -->|"categorized by"| CustomMetadata

This diagram shows how the Repository Model connects business systems and integrations to technical services and endpoints, enriched with documentation and metadata.

You can also visualize your integration landscape interactively:

Integration Landscape of INT1001: Contoso Orders to ERP with the Systems Contoso ERP and Contoso Webshop, their Services and Contract with monitoring states, the canvas toolbar, and the Artifacts column (7.12)
The Nodinite Integration Landscape of INT1001: Contoso Orders to ERP.

When you have the right permissions, you access information directly in Log Views and Monitor Views. Nodinite includes all Repository Model data in Monitoring Alerts from Alarm Plugins.

The Nodinite Repository Model provides CMDB features and includes the following User-defined artifacts:

Repository overview, first rows: Integrations to Templates (7.12)
The Repository overview: one card per artifact, with its count and an Add button.

Repository overview, last rows: Document Profiles to Custom Metadata (7.12)
The last rows, from Document Profiles to Custom Metadata.

Core Services Web Client User Guide Add or Manage Delete and Restore (Administration)
Integrations Integrations Overview Add or manage Integration Manage Integrations
Systems System Overview Add or manage System Manage Systems
Services Service Overview Add or manage Service Manage Services
Endpoints Endpoints Overview Add or manage Endpoint Manage Endpoints
Message Types Message Type Overview Add or manage Message Type Manage Message Types
BPMs BPM Overview Add or manage BPM Manage BPMs
Domains Domain Overview Add or manage Domain Manage Domains
Architecture Diagrams C4 Diagrams Overview C4 Diagrams Overview
Component Types Component Types Overview Component Types Overview
Images Images Overview Images Overview
Files Files Overview Files Overview
Custom Metadata Custom Metadata Overview Add or manage Custom Metadata Manage Custom Metadata
Custom Fields Custom Fields Overview Add or manage Custom Field Manage Custom Fields
Articles Articles Overview Add or manage Article Manage Articles
Tags Tags Overview Manage Tag

Administrators and users whose Role may change the Repository find every management page in Manage the Repository.

The cards on a view page (and the Repository Model tab of a Log Event) list related items by name. The name of each Service, System, Message Type, and Endpoint is a link to that item's own view page, in the same tab; the card's Edit button opens the edit page in a new tab. If your Role may not open the item's page, you see its name as plain text. This lets you move quickly through large amounts of configured data.

Repository Model Data in Monitor Views

With the right permissions, you see Repository Model data in Monitor Views where you associate one or more Integrations. The Monitor View Contoso: Orders on its Repository Model tab, next to Live Monitor, Monitor View History, Resource History and Distributed Notifications, showing the Integration INT001: Orders (7.12) Repository Model tab in a Nodinite Monitor View. The tabs are Live Monitor, Monitor View History, Resource History, Repository Model, and Distributed Notifications.

The Repository Model content appears in the 'Repository Model' tab. The Integration INT001: Orders as the Repository Model tab shows it: description, wiki link, Tags, Integration Landscape button, and Custom Metadata with SLA level Gold (7.12) Repository Model data example.

Repository Model Data in Log Views

When bound, Nodinite Repository Model data displays on Logged Events in Log Views. Click the square button with a caret (, tooltip Show Details) to the left of the Action button: A logged event row (Order Invoiced, ORD-10001) with the Show Details button to the left of Action (7.12) Log Events details button.

Then, click the Repository Model tab to view the content. The tabs of the details are Search Field Values, Additional Field Values, Context Values, Repository Model, and Comments. The details of the Order Invoiced event on its Repository Model tab: Transport Contract, Service INT1337-INV-Order-Invoiced with its System ERP-Finance and BPMs, and the Integration INT1337 - Order-to-Cash (7.12) Repository Model tab and example data in a Log View.

Nodinite makes the association with Transport Contracts that you bind to one or more Services and Contracts.


Reports and Data Sharing

All Data in the Nodinite Web Client comes from the Web API. You can create Reports on the same set of data. If you have limited access in the Nodinite Web Client, you get the same limited data using the Nodinite Web API.

For example, use Microsoft Excel or any other tool that works with JSON data. Copy the data address from the Copy API URL button in the page toolbar. You find it on the lists in Administration, on Repository lists such as Services and Systems, and on a Log View's search result. The Repository > Integrations list doesn't have it; use Administration > Integrations.
The Copy API URL button (7.12)
Copy API URL button.

From the Copy API URL modal, choose to copy the address for either the current filtered result (what you see) or the unfiltered data (ALL).
The Copy API URL dialog from Administration, Integrations: the tabs URL - Current resultset and URL - Complete resultset, the address with a copy button, and Close (7.12)
Copy API URL modal.

  • Tab: URL - Current resultset
  • Tab: URL - Complete resultset

Next Steps