Enterprise messaging is a critical enabler of distributed business applications. The Java Message Service (JMS) is a set of standard, vendor-independent interfaces that integrate distributed business applications by enabling the guaranteed, asynchronous exchange of messages between independent Java programs through a central messaging server. This article introduces you to the JMS support included in SAP Web Application Server (SAP Web AS) 6.20 and higher. It shows you how to build JMS messaging into your custom SAP Web AS Java applications, helps you avoid some unexpected behaviors and common JMS performance pitfalls, and highlights issues that can be confusing for those new to JMS.
Sabine Heider
Sabine Heider is a member of SAP’s Java Server Technology group, and since 2002 has worked on the integration of the JMS provider into SAP Web Application Server, as part of the JMS project. Sabine started her career with SAP in 1997 as a developer with the porting team for the DB2 on OS/390 database platform. After three years in that position, she supported strategic development projects as a technical solution specialist. Prior to joining SAP, Sabine studied physics at the University of Bonn, Germany, where she received her diploma in 1995.
You may contact the author at sabine.heider@sap.com.
If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.
Radoslav Nikolov
Radoslav Nikolov graduated with a degree in mathematics from Sofia University, Bulgaria, after completing a master’s degree thesis on multimedia message services. He joined SAP Labs Bulgaria at the end of 2002 after working for a consulting company. Radoslav is currently a member of the Java Server Technology group, where he leads the JMS development team.
You may contact the author at radoslav.nikolov@sap.com.
If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.
Michael Koegel
Michael Kögel studied technical computer science at FH Konstanz in Germany. After completing his thesis on distributed computing with Java and receiving his diploma in 1998, he worked as a consultant on several major projects in banking, financials, and telecommunications. In early 2003, Michael joined SAP’s Java Server Technology group, where he is currently leading the JMS project.
You may contact the author at michael.koegel@sap.com.
If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.