Integrated Landscape Visualization
Are you tired of trying to understand the complex web of connections between the various systems in your organization? Do you struggle to keep track of how each system fits into the bigger picture?
This tool is here to help! It takes in information about the links between the various systems in your organization through a simple API interface, and automatically generates a visually appealing graph that clearly illustrates the relationships between the different systems. No more sifting through confusing spreadsheets or trying to make sense of disorganized documentation - the graph provides a simple and intuitive way to understand the landscape of your organization's systems.
And that's not all - this tool also gives you the ability to export the landscape in table format to a PDF, making it easy to share with your colleagues or keep a record of the relationships between the systems. Plus, with the API interface, it's easy to integrate my tool into your existing workflow and keep your system landscape up to date.
This tool is easy to use and requires no technical expertise to understand. Simply input your information through the API interface and let the tool do the rest. You'll be able to clearly see the relationships between the different systems, giving you a better understanding of how they all fit together.
Don't waste time in trying to piece together the puzzle of your organization's system landscape start using this tool today, send me a message through LinkedIn and I will help you setting it up.
Want to read more information on how you can use this tool, see Info on Integrated Landscape Visualization. For a live version of this tool, with which you can play, use Integrated Landscape Visualization.
How to integrate this tool in your deployment workflow
Important Guidelines:
- Unique Identification: Each Node, Subnode, and Interface within an Environment is uniquely defined by its name and version.
- Appropriate Use of SubNodes: Utilize SubNodes only when they are responsible for creating or interpreting the interface and can be deployed independently of the Node they are associated with. Avoid using SubNodes unnecessarily to maintain simplicity and clarity.
- Optional SubNodes: Adding one or more SubNodes to a Node is not mandatory. A Node can function as both a source and a target and may include one SubNode if needed.
API Call Usage
Before integrating a new interface into your CI/CD environment, you must manually create the necessary links. Follow these steps:
- Create Links Manually: Use the appropriate API calls to add a source, interface, and target. Then, connect them using the Link call.
- Integration in CI/CD:After establishing the links, incorporate the POST calls into your CI/CD environment to upload a new version of your application (source or target) or a new interface.
- Version Management:Utilize the "keepVersions" query parameter to specify whether the previous version of your application or interface should be retained or deactivated.
Definitions
| Term | Definition |
|---|---|
| Node | A system or application running within your environment. |
| SubNode | An application or module that is part of a Node. It can only be attached to an existing Node within this tool. |
| Source | Is the Node or SubNode that is sending the information |
| Target | Is the Node or SubNode that is receiving the information |
| Interface | An information flow (e.g., file, API, database, stream) sent from a source to a target. |
| Link | A unique combination of a source, interface, and target. |
| keepVersions | An enumeration used to specify whether previous versions of a Node, SubNode, or Interface should remain active when a new version is added. |
Viewing Your Environment
Only Links are displayed in the Table and Graph views. To visualize your landscape, you must add these links. Before adding a link, ensure the Source, Interface, and Target are already included in the tool.
For optimal usage, follow these steps:
- Manual Addition: Initially, manually add a Source, Interface and Target using the Swagger page.
- Manual Linking: Use the GUI, table view, to create new Links.
- Automatic Maintenance: Once the Link is established, you can maintain it automatically by integrating the POST API calls for the Nodes, SubNodes, and Interfaces that are part of the link.