Chapter Eight. Java-Based Middleware Standards and Application Integration

What does Java have to do with application integration? The answer is, "A lot." As we move to ward middleware standards, we find that most of them, including JMS, JDBC, and JCA, are Java based.

Java is not a "cure-all" for application integration, but there are many related standards that are applicable in more than just a few problem domains. In addition, as Java standards become more accepted, traditional application integration vendors continue to adopt Java-based middleware standards and build them into their products.

This is an important chapter, as is the chapter on JCA (Chapter 10). Once again, just the relevant information will be presented here, including what works where. There are many books on Java middleware you can use as a reference, and you don't have to be a Java expert to get some good information here.

Java-based middleware standards have been with us for some time now, so what is new to tell? To begin with, the standards are always evolving, new capabilities are published monthly, and application integration vendors are moving quickly to support these capabilities.

The latest Java standard, JCA, is clearly a revolution for application integration.We also have JDBC, EJB, JMS, RMI, and even Java-to-XML standards such as JAX. Java is no longer just a language and a virtual machine, but a group of inter-related standards that vendors and architects can leverage within a solution set. In fact, it does not matter if Java is your language or platform of choice. You can mix and match Java and non-Java standards to solve your application integration problems.