- 0 minutes to read

๐Ÿ“š The Power of the Nodinite Repository Model

Integration Landscape
Here's an example of the Integration Landscape that you can sculpt by hand or use automation and the Web API or even better, you wrote the system integration solutions and know all the nitty-gritty details, why don't you pass that data (Context Options) along together with the Log Events?!

Turn Your System Integration Documentation into a Live Asset

๐Ÿ”Ž Do you even know how many system integration solutions you have?

With the Nodinite Repository Model, Users gain real-time visibility and control over entire the entire Integration Landscape. Unlike static documentation (Word, Visio, Excel), the Nodinite Repository Model is an active, CMDB-inspired database that keeps your integration portfolio up to date.

๐Ÿ“Œ Key Benefits:
โœ… Instant Access to Integration Data โ€“ Know where your integrations are deployed, their SLA levels, system owners, and more
โœ… Embedded in Alerts โ€“ Automatically include Custom Metadata in notifications for faster troubleshooting
โœ… Seamless Incident Management โ€“ Webhook-based automation enables instant updates to your ITSM or monitoring system
โœ… Unlimited Data at No Extra Cost โ€“ Create and share unlimited repository entries without additional licenses
โœ… Full Automation Support โ€“ Utilize the Nodinite Web API to auto-populate data and integrate with external systems

What is the Repository Model?

graph RL subgraph "Repository Information Providers" roBusinessDemands(Business/HR/Legal
Formal and informal) roPL(Project Management
ICC/Service Owner) roArch(Enterprise/Solutions
Architects) roDeveloper(Developers) roBusinessDemands ---roPL roPL ---roArch roArch ---roDeveloper roTest(Testers) roDeveloper ---roTest roITOPS(IT Operations) roTest ---roITOPS roAM(Application
Management) roITOPS --- roAM end roRepository(fa:fa-sitemap Repository) roBusinessDemands ---roRepository roPL --- roRepository roArch --- roRepository roDeveloper ---roRepository roTest ---roRepository roITOPS ---roRepository roAM ---roRepository

The Nodinite Repository Model provides an organized, structured way to document system integrations using Custom Metadata. This means you can dynamically track and categorize your integrations based on:

  • Deployment environments (Prod, Test, Dev)
  • SLA levels (Gold, Silver, Bronze)
  • Technology stacks (BizTalk, Mule, Logic Apps, Kafka, etc.)
  • Owners and responsible persons (John Doe, Jane Doe, etc.)
  • Business systems involved (ERP, HR, MES, CRM, etc.)
  • And any other attributes you define!

Repository Model

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 artifacts

Visualizing Your Integration Landscape

๐Ÿ“Œ The Repository Model allows you to:

  • Create a visual integration landscape using interactive dashboards
  • Structure data with a graphical model and tabular formats
  • Automatically include metadata in alerts and monitoring events
  • Integrate seamlessly with incident management tools via webhooks

๐Ÿ’ก If everyone contributes to the Repository, the entire organization benefits. No more lost documentationโ€”get instant insights when and where you need them!

Supercharge Your Incident Management Process

โณ Every second counts when an incident occurs.
With Nodiniteโ€™s Repository Model, all critical metadata is automatically embedded in alerts. When an integration fails, your team instantly gets essential details such as:

๐Ÿ”น Affected system(s)
๐Ÿ”น Responsible team or owner
๐Ÿ”น Service level agreements (SLAs)
๐Ÿ”น Integration type and dependencies

  • ๐Ÿ›  Automate Incident Handling:
    • Webhooks enable direct integration with your ITSM system (ServiceNow, Jira, etc.)
    • Reduce manual lookups โ€“ all required information is instantly available
    • Accelerate resolution times by eliminating delays caused by missing documentation

๐Ÿš€ This automation reduces downtime, improves efficiency, and ensures a smooth troubleshooting process.

One Click Away: Repository Data Everywhere

๐Ÿ“‚ Access repository data instantly within:
โœ… Log Views โ€“ Use repository data as search filters to quickly find relevant logs
โœ… Monitor Views โ€“ View and analyze integrations directly in the monitoring dashboard
โœ… Alerts & Notifications โ€“ Receive enriched incident notifications with complete context using any of the Nodinite Alarm Plugins

๐Ÿ“Š Beyond Documentation โ€“ A Foundation for Reports & Insights

  • Use repository data to generate custom reports
  • Improve governance and compliance with structured, traceable records
  • Enable collaboration by sharing data across teams without additional licensing costs

Why Choose Nodiniteโ€™s Repository Model?

๐Ÿ“Œ Designed for modern system integration landscapes
๐Ÿ’ก Eliminates knowledge silos & enhances collaboration
๐Ÿ”— Fully integrated with monitoring, logging, and incident management
โšก Increases operational efficiency & reduces downtime

The Repository Model contains the following manageable artifacts:

Entity 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
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