Welcome to the Ignition Architecture Builder forum thread!
What is the Architecture Builder?
The Architecture Builder is a Perspective project designed to help users plan and document Ignition Architectures, from basic setups to more complex, enterprise-level deployments. With its intuitive select-and-place tool, both new and advanced users can create, share, and track architectures—all within a single project. The included Bill of Materials (BOM) view helps monitor server load, using Inductive Automation’s Server Sizing and Architecture Guide to ensure everything runs smoothly as your deployment grows.
How to Use This Thread:
This forum is dedicated to the Architecture Builder and serves three main purposes:
Ideas Board:
Share your feature ideas, improvements, and enhancements you'd like to see added to the Architecture Builder.
Bug Identification:
Report any bugs, glitches, or issues you've encountered while using the tool. Please include as much detail as possible so we can reproduce and fix the issue quickly.
Help and Support:
Need help using the Architecture Builder? Ask your questions here! Whether you're new to Ignition or a seasoned integrator, this community is here to assist.
We look forward to hearing your ideas, suggestions, and bug reports. Let’s collaborate to make the Architecture Builder the best tool for Ignition Architects!
When I was using it when it first came out, I noticed that the reverse proxy didn't allow passing MQTT connections through it. That would be nice to be able to add that as an option/connection type for the reverse proxy.
Reason I ask for this is that HAProxy supports natively passing MQTT through, and other reverse proxies might also, but I use HAProxy so knew it was possible as I've done it.
@michael.flagler, at this point, we have been using the firewall and reverse proxy components as overlays. Our plan moving forward is to add various connection types to these components. However, we need to build both incoming and outgoing relationships for those connections to support a long-term goal we have for the project.
Could I recommend the ability to delete a component using the tree view. Or when you click on the component add a delete function, similar to connections.
It would also be helpful to disallow components being placed outside of the viewable canvas. Not sure how you would get this to work with resizing the canvas though without messing with existing alignments. But I've ran into a couple issues where I go to move a component, and it ends up being placed outside the canvas with no way to delete.
I'm having issues getting this running. I've tried importing it both from the designer and the gateway. The page appears to load correctly for a second then the embedded view shows |URI:|/system/webdev/arch-builder/exchange/pan-zoom-iframe/html| |STATUS:|404| |MESSAGE:|Not Found|
Tried on 2 different machines, and tried both version 1.0.3 and 1.0.4.
Any help is appreciated.