We Are please to present you two 40 minutes videos about OpenESB. The first is named: "OpenESB - Pr…
Working on integration projects, we often faced difficulties with "Data integration". The OpenESB co…
Good news: OpenESB support with Netbeans 7.01 is now ready. You can find this version of Netbeans at…
Pymma is technical architect's office based in UK (London main office), Netherland, France and Canada. Founded in 1999 by a group of technical architects Pymma built a strong expertise in technical architectures based on Java technologies.
Pymma has a strong expertise in Service Oriented Integration with JBI based open source product OpenESB. It participates actively in the OpenESB community by publishing technical papers and tutorials and sponsoring actively the community. Pymma is involved in important JBI /OpenESB/Java CAPS European projects and delivers consulting, training, mentoring, proof-of-concepts (POC), benchmarks and support to its customers along their projects
Pymma partners are mainly senior architects, multi-languagespeakers with an international experience in top European and US companies. They all took part in enterprise wide project as architect
Pymma is a Java certified Enterprise Architect Company, Open ESB partner and TOGAF certified
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]
Every Thing You Always Wanted to Know About BPEL Compensation But Were Afraid to Ask ;-).
BPEL compensation is one of the main feature used to provide consistency in a business process. Unfortunately, BPEL tutorials often skip this part of Oasis specifications. Even if on Internet you can find papers on that topic, few propose a complete and progressive explanation with simple exercises. It is the reason why we decided to write a complete tutorial which covers all the features defined in BPEL Specifications. We hope that this paper will be useful for you. Please send us your feedback and your comment. Link to the document