MQ is an application. Program The communication method of the application. Applications write and retrieve data (messages) for applications in the inbound and outbound queues to communicate with each other without dedicated connections. Message transmission refers to the communication between programs by sending data in messages, rather than by directly calling each other. Direct calls are usually used for such remote process calls. Queuing means that applications communicate through queues. The use of the queue removes the need to receive and send applications simultaneously.
The IBM WebSphere MQ product allows applications to communicate with each other through different components, such as the processor, subsystem, operating system, and communication protocol networks. For example, IBM WebSphere MQ supports more than 35 different operating systems.
IBM WebSphere MQ supports two different application programming interfaces: Java Message Service (JMS) and Message Queue interface (mqi ). On the IBM WebSphere MQ server, the JMS binding method is mapped to mqi. As shown in 3, the application directly communicates with its local queue manager by using mqi. mqi is a group of calls that require the queue manager to provide services. What's striking about mqi is that it only provides 13 calls. This means that it is a very easy-to-use interface for application programmers, because most of the hard work will be done transparently.
Figure 2. IBM WebSphere MQ Programming
Figure 2 shows the principles of IBM WebSphere MQ programming. The first step is to connect the application to the queue manager. It uses mqconnect to perform this connection. Next, use mqopen to open a queue for the output. Then the application uses the mqput call to put the data in the queue. To receive data, the application calls mqopen to open the input queue. The application uses mqget to receive data from the queue.
The figure also shows the Message Channel proxy (MCA), channel egress, and object permission Manager (OAM ). The MCA is an IBM WebSphere MQ program that uses existing transmission services such as TCP/IP and SNA to move messages from the local transmission queue to the target queue manager. These transmission services are channels. The channel egress is written to the database by the user. You can enter these databases from one of the defined locations during the channel operation. OAM is the default Authorization Service for command and Object Management (for the operating system ). These three components are very important to the existing security solutions of IBM WebSphere MQ.