Enter Names of Remote WebSphere MQ Queue Manager

If you selected Remote for your MQ Queue Manager (MQM) in the earlier Oracle Universal Installer screen, then enter the remote WebSphere MQ queue Manager name in the Queue Manager field.

Enter the WebSphere MQ channel name in the Channel field.

What is a Queue Manager?

A queue manager is a system program that provides an application programming interface so that programs can put messages on, and get messages from queues. A queue manager provides additional functions so that administrators can create new queues, alter the properties of existing queues, and control the operation of the queue manager.

For WebSphere MQ message queuing services to be available on a system, there must be a queue manager running:

Many different applications can make use of the queue manager’s services at the same time and these applications can be entirely unrelated. For a program to use the services of a queue manager, it must establish a connection to that queue manager.

For applications to be able to send messages to applications that are connected to other queue managers, the queue managers must be able to communicate among themselves. WebSphere MQ implements a store-and-forward protocol to ensure the safe delivery of messages between such applications.

What is a channel?

A channel is a logical communication link. There are two different categories of channel in WebSphere MQ, different channel types within these categories:

Message channel

This connects two queue managers via message channel agents (MCAs), and is unidirectional. Its purpose is to transfer messages from one queue manager to another. A channel definition exists at the sending end of the link and another at the receiving end.

MQI channel

This connects WebSphere MQ client to a queue manager on a server machine. It is bi-directional and is for the transfer of MQI calls and responses only( including MQPUT calls that contain message data). A channel definition exist for each end of the link, and there are different ways of creating and using the channel definitions (see “Connecting the MQSeries client and server-channel definition” in the book WebSphere MQ Intercommunication for details). For PG4MQ, we use MQI channel.

Channel definitions, of both categories described above, must include a channel type as well as a channel name. You can choose to use different channel types according to the application you are designing, but the same channel name must be used at both ends of each combination.

Message channel types

These are not required in the WebSphere MQ client and server environment. See the book WebSphere MQ Intercommunication for details.

MQI channel types

There are two channel types for MQI channel definitions. They define the bi-directional MQI channel.

Client connection

This type is for the WebSphere MQ client.

Server connection

This type is for the server running the queue manager, with which the WebSphere MQ application, running in a WebSphere MQ client environment, will communicate.

MQI channel defined in PG4MQ gateway initialization (the MQSERVER parameter)

It specifies the location of the WebSphere MQ server and the communication method to use. The format is channel_name/connection_type/hostname[(port_number)].

For example:

MQSERVER = CHANNEL1/TCP/dolphin(1425)

Click Next to continue.