ns, thus, are developed especially to provide solutions to quite specific problems.
Design patterns are standard application scenarios, that are commonly encountered, and for which the message queuing design has already been developed. Design patterns frequently can provide a complete solution for an application. Alternatively, design patterns can provide a strong starting point for the development of a more sophisticated design.
Most message queuing applications tend to follow one of a small number of design patterns. These design patterns facilitate decision-making related to the selection of product features. The design patterns also define the process for handling specific messaging errors.
4. Designing for Heterogeneous Networks
Distributed applications based on message queuing may be deployed across different kinds of computer systems. Different computer systems represent data in different ways. Further, the preferred development environment and programming language varies from system to system. Differences in data representation and in programming language can significantly complicate the task of building a working application. The best way to overcome such problems is to design messages to be exchanged in a process that observes the following rules:
The first rule is to use only character data in messages. Character data are handled almost identically regardless of the programming language being used. Character data also are the easiest to translate between different machine representations. MQSeries can perform such translations automatically.
The second rule is to avoid null-terminated string representations of character data. Using fixed-length character arrays without terminating characters is more portable among different systems.
5. Creating Inquiry-Style Applications with MQSeries
In inquiry-style applications, a client program requests information from a server. Frequently, the cli...