Chapter1 ----- MQSeries Series Products Introduction MQSeries and Message Queuing Messages and Time-independent application messages Drive Processing Process messages and queues What is a message? 1. Application Data 2. The length of the message descriptor message requires the number of applications required
It may take several messages to be complete. What is the queue? It is a queue structure used to store messages. Queue Manager needs management
The queue it has. How does the application send, receive a message? Predefined queues and dynamic queues (in accordance with their creation) compare predefined queues
The existence time and the existence time of permanent properties in the dynamic queue! One is existed when the MQ product is started, and the addition is the queue belonging.
The manager is only available. Retrieving back from the queue 1 Message 1 First-first out - out Algorithm 2 Priority Algorithm 3 Search MQGET Functions for Clear Messages
The parameter can indicate the search algorithm used by the program! Objects include queue managers, queues, process definitions, channels (pipelines), clusters, and namelists.
Operation and management of objects! The uniqueness of the object name queue manager name is unique in a queue manager! (Just not
The parameter name of the same partial function can be the same! ) The name has up to 48 characters. WITH The Exception of exceptions are pipelines
There are up to 20 characters. Administrative objects use scripts to execute commands (MQSC) by the MQ used in the Control Commands program.
Management Interface Call Objects There are two ways in MQ to see Properties 1 PCF name (formal name) using properties 2 2 Use MQSC Name Queue Manager 1 Task 2 Task 2 Local Queue Manager has a remote queue relative to remote queue And remote queue management
Serve: The remote queue manager is any queue manager than the local queue manager. A remote queue manager can exist from far in the network
On the main unit, you can also exist on the same machine and the local queue manager. MQSeries supports multiple queue managers on the same system.
You can query the properties of the queue manager object via MQINQ. Note that the queue object and the queue manager object are different. MQSeries Queue 1. Use the appropriate MQSC define command to define queues; 2. Create queue commands with PCF to define queues. The command determines the type and attribute of the queue. For example, when an application queries this queue through the MQI call, the local queue object is
There is such an attribute to specify the corresponding trigger process response. The example is as follows: When the get command, the application can retrieve a message from the queue; when the put command, the application can put the elimination
Interest in the queue; the entry of the queue is exclusive or shared by multiple programs (critical resources); one-time can be stored in the queue
The maximum number of messages (or called queue depth); the maximum depth of the message sent in the queue. Using the queue object in the MQ series, there are four types of queue objects. Each type of object can be commanded by commands, and
The corresponding real queue is associated. 1 Local queue object The local queue object determines a local queue from the queue manager connected to the application. All queues belonging to a queue manager are
Local queue. 2 The remote queue object A distal queue object determines a queue belonging to another queue manager. For this queue manager, this queue should be its local team
Column. When you define a remote queue object, you should allow the local queue manager to find the corresponding remote queue through your definition information.
Instruments, such any messages sent to the secondary queue can be transmitted to the correct queue manager. (That is, the information must be placed in a specific queue through the manager) You must first
First define the transmission queues and channels between a queue manager. Otherwise, you will bind these queue managers as a cluster (Cluste
r). 3 Alias queues One different queue allows the application to call a queue when the application uses MQI calls. This is a bit similar to (just similar to)
Sub-state! Just at runtime, the alias in the MQI Call is parsed to the real local or remote queue. This makes you can pass only
Only change the definition of the alias queue to change the goal of changing the queue you really want to call; do not have to change the program itself. The alias queue is essentially not a queue, but a way you use to enter the queue in other queue managers. 4 Queue Template Objects It defines a group of queue properties that can be used as a template to create a dynamic queue. When the application issues MQOpen request to the queue manager
When the specified queue name is the name of the queue template. Create a dynamic queue through this command. Its attribute is inherited from the template definition
. Its name can be specified in advance or returned to the application after being generated by the application or queue manager. The specific local queues used by MQSeries must define the local queue in advance, and MQSeries use them to complete special purpose. 1 Application Queue Application Queue is a queue called by the application via MQI. It can be both a queue in the local queue manager, or a remote team
The queue in the Column Manager. Applications can put messages into remote or local queues, but it can only get messages from the local queue. 2 The initialization queue initialization queue is used to trigger a certain behavior. When the trigger event occurs, the Queue Manager puts a trigger message into the initial queue.
in. The trigger message is a collection of various situations detected by the queue manager. For example, when the number of messages in the queue reaches a predefined depth
Generate a trigger event. This event allows the queue manager to put a trigger message to a dedicated initial queue. This message is touched
The Trigger Monitor is retrieved, a program specifically used to monitor the initialization queue. Then, the monitor will start
A corresponding specific application to handle this message. ? 3 Transport queues It is a queue for temporarily storeing messages that go to the remote queue manager. You must define at least one for each remote queue manager
The transfer queue so that the local queue manager can send a message directly to the far end. These queues are also used in remote management. 4 Cluster Transport Queues have a cluster transfer queue in each queue manager in the cluster, called: system.cluster.transmit.queue. This
The definition of the queue is the default in each queue manager of the MQSeries product on various operating systems. Queue manager in the same cluster
You can send messages to other queue managers through this cluster transmission queue. And the cluster queue manager can also be in different clusters
Queue Manager communicates with each other. Of course, first, you must first define the channels and transmission queues of the join other queue managers. This is similar to the traditional division
Flite queue environment. At the name analysis, the cluster transmission queue takes precedence over the default transmission queue. When a queue manager other than a cluster is removed from the remote queue
Interest, use the default transmission queue if there is no transmission queue with the same name as the destination queue manager. (? Is it associated with this remote
Queue Transfer Queraries) When the queue manager is a part of the cluster, the default operation is to use System.Cluster.Transmit.Queue's cluster transfer team.
Columns, unless the destination queue manager is not a cluster. 5 Dead letter queues It is a queue that stores messages that cannot be sent to the correct destination. This happens, for example, the destination queue is full, this
When you send a message in the inside, you will definitely get it. The dead letter queue used to supplement is called System.dead.Letter.Queue. The dead letter queue sometimes refers to the queue that is not delivered. For distributed queues, you have to define a dead letter queue for each queue manager. 6 Command Queue Command Team Name is System.admin.command.queue. Authorized programs can send it to it to be processed MQSeries commands. These orders
Subsequently, the Commands Server by MQ, Command Server activates these commands to process them to the queue manager.
Returns any reply-to queue to the appropriate response. The command queue is automatically created when the queue manager is created! 7 Feedback Queue (Reply-to) When an application sends a request message, the recipient will feedback a message to the sender. This message is placed in a queue
The feedback queue is called a feedback queue. It is usually related to the local queue of the sender, and the name of the feedback queue is a message in sending a message.
The sector is specified in the descriptor. 8 Records of the Instrumentation Events in the Event Queue MQSeries V5 product. In this way, we can do not rely on the MQI application
The order to monitor the queue manager. There are many cases of equipment events: - try to send messages to unsavailable queues;
Queue; - the passage being started. When a device event occurs, the queue manager will place an event message in the event queue. If this message hints a problem,
Programs responsible for monitoring this queue will notify the administrator or start the remedy. Note: Trigger events and device events are very different
. In the same case, there is no trigger event, but an event message can be generated. vice versa! Program definition program definition object details the application used to respond to trigger events in the MQ queue manager. Program definition attribute includes program ID
, Program type, specialized data useful for programs. You can use the MQSC command define process or the command in the PCF format to create
Ordered definition. Channel channel object provides a path between the communication communication between the queue manager. It is used to pass between different queue managers in the distribution message queue
news. They shield the underlying communication protocol for the application. These queue managers can exist on different, the same platform. you want
Define a channel object to the sending end in the manager that communicates with each other, defines a reverse, complementary channel object at the receiving end. In this way
Can make both each other. The cluster is in the traditional MQ network, which is the use of distribution queues. Each queue manager is independent. If a manager needs to send it to another
Interest, you must first define a transmission queue, a channel of a remote manager, and a remote queue definition. So groups, is a group of queues management
In a single network (my understanding is the queue management that can communicate with each other with the same network protocol and OS platform)
Collection of instruments. This avoids complex transmission queues, channels, and queue definitions. Name table named table object includes a list of other MQ objects. Typically, named tables are used by applications such as trigger monitoring. Use the name of the named table
The potential is that it can maintain independence with the application. That is to say, can be updated without stopping any applications using it.
Once a program of a related named table hangs, other programs can still use the named table. Naming tables are often also used in the queue manager cluster. It allows you to maintain a cluster list of more than one MQSeries object. System Default Object System The default object is a set of object definitions that automatically created when the queue manager is created. You can copy when installing your app
And modify the definition of any object. The default object name is SYSTEM.DEF word dry. For example, the default local queue is
System.default.local.Queue; The default reception channel is System.def.Receiver. For these objects, you can't be renamed. When you define an object, any properties you don't have clearly specified will be copied from the default object. For example, you define one
This queue, these do not explicitly specify the attributes will inherit from the System.default.local.Queue queue. (I'm here
Use the word "inheritance", actually refers to a complete replication) 46/445
