OpenESB Components build process is a bit tricky and stops developer in fixing and implementing improvement. This document explains in detail, the process to build OpenESB component and create a deployable components for OpenESB. This process can be used for services engines and binding component. We hope that this document will push developers involvement in fixing and improving OpenESB components
Please download the document here
You love OpenESB, but you never have time to explain to your colleagues, managers, mam or girl friend, how it works. We propose you a tutorial for them. This document is a hello world step by step guide for OpenESB new joiners. We hope they will enjoy it ;-)
The installation guide can be download here
By interfacing Opview and OpenESB, you monitor OpenESB with a global enterprise monitoring tools at the same level as the database, infrastructure, Operating Systems. This OpenESB capability is appreciated by support and production teams and promotes OpenESB adoption as enterprise tool. This document describes guidance on how to set up Opsview to monitor OpenESB. It is a tricky work that needs initiative from the reader to adapt our document to his own working context. It is the excellent job made by Simon Steinmetz from Ineat Conseil (http://www.ineat-conseil.com/) who wrote a more formal document on the same topic. Link to the document . Here is Simon's document
This paper explains how to set up the JMS Binding Component and connect OpenESB applications with an external Open MQ brokers cluster in High Availability mode (External means not embedded in Glassfish Application Server). We test how the connection between the binding component and the cluster behaves when one or more brokers fail in the cluster.
Our objective is to specify how to configure OpenESB JMS BC without using Glassfish Server abilities. We tested two JMS BC configurations. The first relies on JMSJCA technology. Very easy to configure it is used as reference in many OpenESB lessons and tutorials. The second configuration relies directly on java naming API (JNDI) to access to the broker. Here, connections to the brokers are defined by the Connection Factory and destination object parameters. Even if using JNDI configuration is a bit more complex but is centralised in a shared file or an LDAP server. Our tests did not highlight difference between the two configurations. Both configurations provided a real High Availability. [If someone get other results to his/her tests, we will be very pleased to have a discussion and exchange ideas and results. Please contact us at: contact (at) Pymma.com]