The documentation needs to be better — maybe they could add more accurate tutorials. However, since I have been working with the product for a long time, it is not a big concern for me, but for the new generation, this could be a problem. Also, the launch took a while, but once we understood the concept of interface services, it became really powerful.

Cloud deployment is weak and needs to be improved. 

The documentation of the product must be improved. It could be tricky to find the right documentation on a topic since the documentation is spread in many places. A part of the current documentation has been written by Sun microsystems and now belong to Oracle. it can be found on the Oracle website. Another part has been written by the OpenESB community and many other documents come from Pymma and Logicoy. So, I advise the new joiner to contact the community to get entry points and accurate documentation. The OpenESB is working on that issue with professional technical writers.

Additional tutorials and Videos to take up the product would be welcome.

Additional components such as a rule engine are welcome. If Connector to Kafka or Apache Gemfire is available, additional connectors to NoSQL containers such as Mongo and Cassandra would be useful.

The Studio is a good tool based on NetBeans, but some of its features have to be improved, liked local schemas management.

As an additional feature, I would request an inline XSLT editor. It does not have to be a full WYSIWYG XSLT editor, bus it should make it easy to use or implement simple XSLT without needing to use an external tool.

Regarding HL7, it has a basic HL7 FHIR Support thanks to the new REST BC, but some features have to be added to make it easier to use OE as a FHIR facade.

Regarding its management, a web console being able to synchronize distributed instances would be great.