Repository Model

Do you even know how many system integration solutions you have? With the Nodinite Repository Model you have an Active definition of your service portfolio using Custom Meta Data and can answer exactly how many system integration flows you have, for example:

  • Deployed in Prod, Test, ...
  • With SLA Level Gold, Silver, ...
  • Running in BizTalk 2013 R2, 2016, Mule, Logic Apps, ...
  • The ones John/Jane Doe is responsible for
  • The system owner for HR, ERP, MES, ...
  • ... You can define your own attributes and twist and turn the Custom Meta Data as you find fit

Integration Broker
LandscapeExample
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 you know all the nitty gritty details, why don't you pass that data (Context Options) along together with the Log Events?!

You and everyone else will get the most out of the Nodinite Repository if everyone contributes starting with the business having a need all the way through the implementing project ending in a running solution that needs supports and maintenance until retirement. Nodinite Repository provides a unique way of sharing active information and replaces your traditional static word, visio, powerpoint, excel documents that gets lost or is unavailable or even worse unaware the information even exists when needed the most. Our Repository is also better than having your system integration solutions documented in Wiki or sharepoint sites due to how Nodinite at all times with just one click have the relevant information available without having to search for the data. The Nodinite Repository even provides this information in Alerts and an example would be an email with all the attributes (Custom Meta Data) provided (for example 'SLA Level: Gold').

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 allows your stakeholders; Users to gain access and insights to your valuable documentation. Sharing this information and creating a foundation for true co-operation when and where needed. You can even visualize your documentation using both the power of graphical models and tabular formats. The plugin based alert engine sends the repository data directly to you, no need to spend time on asking and searching for the documentation. Saves your frustration, time and thereby money.

Documentation for System Integration Solutions are provided by populating the Repository model. The Repository Model is accessed by users with administrators privileges. Nodinite provides this information for any Users using Log Views and Monitor Views.

Do invest in our Repository model and you will be rewarded instantly with helpful information when needed the most

The Repository model provides:

  • Key for support and maintenance
  • Personal independence - Sharing is caring
  • Save time by having information at your fingertips. The Repository information is one click away within:
  • Helps you document your processes using a generic model for System Integration solutions
  • Foundation for reports

The Repository model contains the following Nodinite defines artifacts:

Repository Model

The Repository Model contains the following manageable 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
Message Types Message Type Overview Add or manage Message Types
Custom Fields Custom Fields Overview Add or manage Custom Field
Custom Meta Data Custom Meta Data Overview Add or manage Custom Meta Data
Articles Articles Overview Add or manage Article
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

Manage Integrations

What is an Integration anyway? Find out how we at Nodinite defines an Integration and learn how get the most of your Repository Model by continuing to read how to Manage Integrations page.