How we can help you?Entando FAQs
Can Entando be integrated with other systems, and how?
The modular architecture does allow users to build a connector to any other solution, as Entando interacts through APIs with any system. Out of the box, Entando integrates with Red Hat’s Process Automation Manager.
How do I build an internal marketplace for my enterprise's Entando tools? Where do I run it?
Entando components, plugins, widgets, and UI bundles are all built to be decoupled and deliverable as independent assets. Once an Entando asset (plugin, widget, UI-bundle) exists, anyone at your enterprise can port it into their own Entando application. The assets are stored in a repository and can be reused and added to any new implementation. The marketplace in this case is the ability to create and publish your Entando assets for reuse across all of your applications.
What is the Digital Exchange and why is it cool?
The Digital Exchange allows you to automatically install your Entando components for quick reuse in all of your Entando applications. The Entando Digital Exchange exposes the ability to package your Entando components in an online marketplace for automated discovery, installation, and reuse in the Entando App Builder.
Are different versions of Entando backwards compatible?
Everything for the same major release is compatible. Entando is following semantic versioning for releases of the platform.
Where can I deploy Entando?
Entando can deploy to a private cloud, public cloud, or on the local infrastructure that makes sense for your use case. Entando provides out of the box deployment on AWS and Azure using Kubernetes. Entando also provides images and documentation for deploying on OpenShift. Additionally, we provide Docker images, extendable base Docker files, and examples that use Docker Source-to-Image (S2I). See section 2.5 at docs.entando.com for more information. In most cases, including the cloud cases above Entando is deployed in a J2EE container like JBoss EAP, Wildfly, or Tomcat.