Exchange, modify and aggregate messages between systems!
The Frank!Framework is a framework that is completely configurable through XML configurations. Each Frank!Application may contain multiple configurations, and each configuration can consist of multiple end-to-end connections which we call 'adapters'. Configurations may be (re)loaded conditionally or individually for optimal performance and customizability. The application may be managed and monitored through a web interface or REST API. See it in action: https://frank2example.frankframework.org
The Frank!Framework can run on any Java runtime version 25 and up, either as a standalone Spring Boot application or as a WAR file deployed inside an application server.
The Frank!Framework can be deployed as a WAR file in any application server supporting WAR file deployment. In our CI we test every PR and Release against Tomcat, Wildfly and JBoss, all these application servers are supported by us for use in production environments. Other application servers should work but are untested by us. You may create containers to run the framework using the beforementioned application servers. Please note that they are for development use only, more info about using and creating them can be found in DOCKER.md.
All production-ready containers will be pushed to our Nexus Repository Manager frankframework-docker repository. Helm charts are available in the charts repository.
The Frank!Framework is built using the features of JDBC4.2 and has built-in support for MS SQL Server, Oracle, PostgreSQL, MariaDB and MySQL. Every PR and Release is tested against these databases. Support for DB2 is provided on an as-is basis.
The Frank!Framework is built using the JMS 3.1 API and should be compatible with JMS client implementations that fully implement this specification. In our CI we test each PR and each Release against Apache ActiveMQ and Apache ActiveMQ Artemis client and server. If you need JMS support in your Frank!Framework deployment, make sure that the Messaging module is included in your deployment, or your project dependencies.
The Ibis Adapter Framework has been renamed to "Frank!Framework". The migration is a work in progress, which is why you may encounter some old(er) names throughout our source code. Don't worry, everything will remain fully backwards compatible!
All our releases can be found on Maven central. Individual builds can be found on our Nexus repository here. For more information about our releases, please visit Insights. Breaking changes can be found in BREAKING.md.
It is important to remember that the security of your Frank!Application is the result of the overall security of the hosting stack; the Java runtime, Application Server, Frank!Framework and your configuration.
It is our responsibility that there are no vulnerabilities in the Frank!Framework itself and all it's Java dependencies. In turn, it is your responsibility to keep your Frank!Framework version up to date and ensure there are no vulnerabilities in your configuration. More information about reporting vulnerabilities, supported versions and how we deal with CVE's can be found in our Security Policy.
For bug reports and feature requests, create a new issue at https://github.com/frankframework/frankframework/issues. For general questions feel free to post them on our discussions forum here on GitHub. If you would like to report a vulnerability, or have security concerns regarding the Frank!Framework, please email [email protected] and include the word "SECURITY" in the subject line.
In need of help? You can find our docs portal at docs.frankframework.org. If you cannot find an answer to your question feel free to submit a question in discussions. If you want to contribute to our manual, the sources can be found here.
Eager to help us expand or enhance our framework? Please read our Code of Conduct before Contributing.
Star the repository to stay current with our newest updates and enhancements!
