- 0 minutes to read

Mapify – Interactive Dependency Visualization

New .7.x

Mapify is Nodinite's next-generation visualization tool, designed to help you instantly understand and explore every dependency in your integration landscape. With Mapify, you see your entire Nodinite Environment as a dynamic, interactive graph where circles and lines connect every entity, making complex relationships easier to grasp in a live relationship canvas.

Mapify brings together configuration data from both Monitoring and the Repository Model, letting you visualize how Agents, Applications, Categories, Resources, and Custom metadata are interrelated. Whether you're troubleshooting, planning, or onboarding new team members, Mapify provides the clarity you need.
Mapify Visualization Example
Example of Mapify's interactive graph showing dependencies between Monitoring Agents, Applications, and Resources.

What the Mapify License Adds

The Mapify feature pack is where the biggest value appears. In practical terms, the license adds four core capabilities on top of your base licensed platform:

  • Mapify Rendering as the interactive View Mode for live, physics-based exploration
  • Saved Views as reusable report definitions, also called Mapify Maps
  • C4 Diagrams for architecture-focused modeling views over Repository entities
  • Component Types icon support in C4 and Mapify visualizations for richer, faster visual recognition

For a precise inclusion table, review the License Options and Feature Matrix.

License Value at a Glance

Capability with Mapify feature pack Why it matters Where to continue
Mapify Rendering Explore the current truth interactively with pan, zoom, and drill-through Mapify Rendering
Saved Views (Mapify Maps) Save and reuse filtered visual reports for recurring analysis Saved Views
C4 Diagrams Communicate architecture with software-system, container, and component perspectives C4 Diagrams
Component Types icon support Improve scanability by adding recognizable visual semantics to selected entities Component Types
Mermaid Rendering (via Repository) Use static diagrams when interactive exploration is not required Mermaid Rendering

Why use Mapify?

Mapify empowers you to:

  • Instantly visualize all dependencies and relationships in Nodinite including Monitoring and Repository Model data
  • Explore your integration landscape interactively with View Mode and double-click navigation through relationships
  • Choose between multiple Mermaid Rendering diagram types to visualize data in the format that suits you best
  • Use Focus Modes to narrow your view and trace integrations end-to-end
  • Print or save your current visualization as an image directly from the interface
  • Filter and customize what's shown: choose entities, skip references, and tailor the view to your needs
  • Generate reports based on custom filters and options with Saved Views (Mapify Maps)
  • Understand interrelated parts of your integration landscape at a glance
  • Perform Remote Actions directly on Resources in Monitoring
  • Navigate deeper into Custom Metadata and Monitoring for actionable insights
  • Visualize Domain knowledge from BPM—see which processes belong to Sales, Warehouse, Customer, and more

✅ See your entire Integration Landscape in a single, interactive graph
✅ Explore dependencies faster with interactive View Mode navigation
✅ Instantly identify dependencies, bottlenecks, and opportunities for optimization
✅ Empower teams to act with live Remote Actions and navigation
✅ Customize reports and visualizations for any scenario
Mermaid Rendering available without a Mapify license
❗Mapify requires an additional licensing fee. Contact Nodinite Sales to enable this feature. Pricing varies with licensee turnover.

Mapify Maps vs View Mode vs C4

Use the following quick comparison when deciding where to work:

Capability Primary outcome Typical user action
Saved Views (Mapify Maps) Reusable reporting scope Save, load, and share query/filter presets
Mapify Rendering Interactive relationship exploration Pan, zoom, drag nodes, drill through current truth
Mermaid Rendering Static relationship visualization Switch diagram type, export, and print
C4 Diagrams Architecture communication Present systems, containers, and components with clear structure

This distinction is also reflected in the License Options and Feature Matrix.

How does Mapify work?

Mapify renders every entity and relationship as circles and connecting lines in an interactive graph. You can:

  • Visualize Monitoring hierarchy: Agent → Applications → Categories → Resources
  • See Repository Model entities and their connections
  • Use naming schemes to divide and group parts for unique visualization (e.g., Subscription/Resource Group/Logic Apps/Workflow)
  • Explore BizTalk Applications with their Receive Ports, Maps, Orchestrations, and more
graph TD subgraph "Monitoring Hierarchy" M_Agent["Agent"] --> M_Application["Application"] M_Application --> M_Category["Category"] M_Category --> M_Resource["Resource (Monitoring)"] M_Resource --> RA["Remote Actions"] M_Resource --> M_Art["Articles"] M_Application --> M_Art M_Category --> M_Art end M_Resource -.->|custom metadata & links| XREF_REPO[["→ Repository Model"]] style XREF_REPO fill:#e8f4f8,stroke:#2196F3,stroke-dasharray:5 5,color:#1565C0

Diagram: Monitoring Hierarchy — Agents contain Applications, which contain Categories, which contain Resources. Resources, Applications, and Categories can all have Articles attached. Dashed arrows indicate a relationship that continues in the Repository Model diagram below.

graph TD subgraph "Repository Model" R_Integration["Integrations"] --> R_System["Systems"] R_System --> R_Service["Service"] R_System --> R_Contract["Contracts"] R_Domain["Domain"] --> R_Service R_Service --> R_Resource["Resource (Repository)"] R_Resource --> CM["Custom Metadata"] end XREF_MON[["← Monitoring Hierarchy"]] -.->|Resource links to| R_Resource XREF_BPM[["← BPM"]] -.->|provides| R_Domain R_Resource -.->|shared with Monitoring| XREF_ART[["↔ Articles"]] style XREF_MON fill:#e8f4f8,stroke:#2196F3,stroke-dasharray:5 5,color:#1565C0 style XREF_BPM fill:#e8f4f8,stroke:#2196F3,stroke-dasharray:5 5,color:#1565C0 style XREF_ART fill:#e8f4f8,stroke:#2196F3,stroke-dasharray:5 5,color:#1565C0

Diagram: Repository ModelIntegrations contain Systems, which own Services and Contracts. Domains (from BPM) also group Services. Services own Resources, which carry Custom Metadata. Articles are shared with the Monitoring Hierarchy (see that diagram). Dashed nodes are cross-diagram references.

graph TD subgraph "BPM" BPMs["BPMs"] --> BPM_Domain["Domain"] end BPM_Domain -.->|used by| XREF_REPO2[["→ Repository Model"]] BPMs -.->|Grouped Log Views| XREF_LOG[["→ Log Views (Logging)"]] style XREF_REPO2 fill:#e8f4f8,stroke:#2196F3,stroke-dasharray:5 5,color:#1565C0 style XREF_LOG fill:#e8f4f8,stroke:#2196F3,stroke-dasharray:5 5,color:#1565C0

Diagram: BPM — Business Process Models define Domains (consumed by the Repository Model) and are the grouping basis for Log Views in the Logging Hierarchy.

graph TD subgraph "Logging Hierarchy" LV["Log Views"] --> LE["Log Events"] LE --> LA["Log Agent"] LA --> LSC["Log Status Codes"] SVC["Services"] --> TC["Transport Contracts"] LE --> TC TC --> MT["Message Types"] TC --> EP["Endpoints"] MT --> SS["Stylesheets"] MT --> SF["Search Fields"] SF --> SFE["Search Field Expressions"] SF --> SFL["Search Field Links"] end XREF_BPM_LOG[["← BPM"]] -.->|Grouped Log Views| LV SVC -.->|defined in| XREF_REPO_SVC[["← Repository Model"]] style XREF_BPM_LOG fill:#e8f4f8,stroke:#2196F3,stroke-dasharray:5 5,color:#1565C0 style XREF_REPO_SVC fill:#e8f4f8,stroke:#2196F3,stroke-dasharray:5 5,color:#1565C0

Diagram: Logging Hierarchy — Log Views (grouped by BPM) surface Log Events produced by Log Agents (with Status Codes). Services own Transport Contracts; Log Events also reference Transport Contracts directly. Transport Contracts define Message Types and Endpoints. Message Types carry Stylesheets and Search Fields, which can have Expressions and Links. Services are defined in the Repository Model.

graph LR subgraph REPO["Nodinite Repository Entities"] direction TB NR_SYS["System
C4 Type: Person · PersonExt
InternalSystem · ExternalSystem
SystemDb · SystemQueue + Ext variants
C4 PersonRole · C4 PositionHint"] NR_SVC["Service
C4 ContainerType: API · Database · WebApp
MessageBus · Microservice
Function · EventStream · FileStore
C4 Technology: e.g. ASP.NET Core"] NR_DOM["Domain
C4 BoundaryType: EnterpriseBoundary
SystemBoundary · ContainerBoundary · Boundary
LaneOrder — per diagram only"] NR_INT["Integration
C4 ComponentType
L3 diagrams only"] NR_CONN["C4 DiagramConnectors
Label · Protocol · IsBidirectional"] end subgraph C4OUT["C4 Model — Rendered Shapes"] direction TB CS_PERSON["Person / Person_Ext
Human actor
internal = blue · external = grey"] CS_SYSTEM["Software System
System / System_Ext
SystemDb · SystemQueue variants
internal = blue · external = grey"] CS_CONTAINER["Container
API · Database · WebApp
MessageBus · Microservice · ...
L2 diagrams"] CS_COMPONENT["Component
Internal module inside a Container
L3 diagrams"] CS_BOUNDARY["Boundary
Enterprise · System · Container · Generic
dashed box wrapping shapes"] CS_REL["Relationship
Rel — directional · BiRel — bidirectional
Label + Technology"] end NR_SYS -->|C4 Type = Person / PersonExt| CS_PERSON NR_SYS -->|C4 Type = System / Db / Queue| CS_SYSTEM NR_SVC -->|C4 ContainerType sets shape| CS_CONTAINER NR_INT -->|C4 ComponentType| CS_COMPONENT NR_DOM -->|C4 BoundaryType sets macro| CS_BOUNDARY NR_CONN -->|Label + Protocol + IsBidirectional| CS_REL NR_SYS -.->|reuses| XREF_SYS[["Systems in Repository Model"]] NR_SVC -.->|reuses| XREF_SVC[["Services in Repository Model"]] NR_DOM -.->|reuses| XREF_DOM[["Domains in Repository Model"]] NR_INT -.->|reuses| XREF_INT[["Integrations in Repository Model"]] style XREF_SYS fill:#e8f4f8,stroke:#2196F3,stroke-dasharray:5 5,color:#1565C0 style XREF_SVC fill:#e8f4f8,stroke:#2196F3,stroke-dasharray:5 5,color:#1565C0 style XREF_DOM fill:#e8f4f8,stroke:#2196F3,stroke-dasharray:5 5,color:#1565C0 style XREF_INT fill:#e8f4f8,stroke:#2196F3,stroke-dasharray:5 5,color:#1565C0

Diagram: C4 Diagrams — No new entities are created. Existing Nodinite Repository entities (System, Service, Domain, Integration) are reused directly; the new C4 properties on each entity (left) determine which C4 model shape is emitted in the output diagram (right). C4DiagramConnectors carries the relationship label, technology, and direction. Dashed cross-references link back to the Repository Model diagram above. Mapify's flexible filtering lets you create reports and visualizations tailored to your needs. Skip lines for references you do not want to see, or focus on specific entities for targeted analysis. When those filters are worth reusing, store them as Saved Views (Mapify Maps).


Domain Knowledge & BPM Integration

Mapify is not just about technical dependencies; it also visualizes business context. By integrating Domain knowledge from BPM, Mapify makes it easy to see which processes belong to Sales, Warehouse, Customer, and other divisions. This helps you understand ownership, responsibilities, and process flows at a glance.
Domain Visualization
Example of Mapify showing BPM Domain relationships for Sales, Warehouse, and Customer processes in an interactive graph.

Licensing

Mapify is provided through the Mapify feature pack.

For the complete comparison of Standard License, Repository only, Mapify, and BPM, see License Options and Feature Matrix.

Component Type support is explicitly described in that matrix as Component Type icon support in C4/Mapify under the Mapify feature pack.


Why choose Mapify?

Mapify delivers:

  • Instant, interactive visualization of your entire Nodinite Environment
  • Interactive View Mode with double-click navigation through dependencies
  • Two rendering options: Mermaid (static, several diagram types, no license) and Mapify Rendering (interactive physics graph)
  • Print and image export for sharing and documentation
  • Customizable reports and views for any scenario
  • Live Remote Actions and navigation for actionable insights
  • Integration with BPM Domain knowledge for business context
  • Scalable, enterprise-ready clarity for complex integration landscapes

Mapify combines repository-driven knowledge, live monitoring, and actionable visualization—giving you a unique, powerful view of your business processes and technical dependencies.


Next Step