J2EE Explorer: using JMS for enterprise message delivery [Z]

In this issue of J2EE pathfinder, Java developers and consultants Kyle Gabhart explained why message service is crucial to the enterprise's architecture, what types of obstacles must your solution overcome, as well as alternative solutions besides Java Message Service (JMS. At the end of this article, he analyzed three available solutions (Simple JMS Client), session beans used in combination with JMS, and message-driven beans ), specific guidelines are provided to measure these options.
When talking about the choice of the message delivery solution, you can find a solution suitable for the enterprise as with gloves. Your messaging framework must be able to communicate with a group of applications and enterprise resources. In addition, the message transmission framework must complete this task quickly and reliably. In addition, in the face of day-to-day harassment and emergencies, it must behave seamlessly.
To select an appropriate message delivery solution based on your needs, you should first have a clear understanding of your enterprise's current composition structure and future development trends. In addition, if you have a thorough understanding of the obstacles that the messaging framework must overcome in achieving the goal, it will be helpful for the selection of solutions. Finally, you need to know the options: available technologies, and the applicability of various technologies to different environments and needs.
In this article, we will describe the above points one by one. The first is an overview of enterprise message transmission. Here we will focus on the role of message transmission in your enterprise and provide some challenges in establishing reliable communication. Next, we will take a quick look at how the J2EE message transmission technology works with message-oriented middleware in a typical enterprise network environment. Next, we will discuss the Message transfer packages of Java Message Service (JMS) and J2EE in more detail. We will discuss the basic objectives and functions of the three types of J2EE message passing clients, and you can also understand the advantages and disadvantages of each type of J2EE message passing client. Finally, we will analyze some common messaging scenarios and solutions, which will help you select the best J2EE messaging solution for your enterprise.
Enterprise Message Delivery 101
The enterprise messaging framework is designed to enable one or more applications to overcome various obstacles for communication. Common barriers include the need for two systems to run at the same time (synchronous communication), and the need for multiple applications to obtain the same message (multiple transmissions). Most systems are heterogeneous to each other, and network faults.
M The architecture of many enterprises relies on message-oriented middleware systems (MOM) to provide message channels for different types of systems. MOM provides a public and reliable way for applications to easily create, exchange, and process messages without considering the implementation details of the message passing client. Messages are sent to the server destination and domain, rather than to the physical address. The message passing client simply declares that it is interested in a specific domain and destination, and provides an appropriate security token to obtain the permission to access the domain, then interact with the message passing server through that destination.