Check with your system administrator to verify that this is the correct port to use.Ĭlick Finish to create your queue manager. This is the default port number for WebSphere MQ. Make sure that Create listener configured for TCP/IP is selected, and enter 1414 for the port number. The following step enables the WebSphere MQ applications that are running on your machine to communicate with other machines. Verify that Start Queue Manager is checked. The next screen indicates the type of logging that the queue manager will perform, and the maximum number of log files that can be produced.Ĭlick Next to accept the suggested values and continue. Check the box to make this your default queue manager. Fill in names for the default transmission queue and dead letter queue.

You can use different names if you choose. The names in the example are suggestions. Using all capital letters for names helps avoid confusion. All names in WebSphere MQ are case sensitive. The name MYQMGR will be used in the following example. Select New Queue Manager from the pop-up menu.Įnter the name for your queue manager.

Some method should be in place in production environments to monitor and process messages in this queue.įrom the WebSphere MQ Explorer window, expand the WebSphere MQ label, then right-click Queue Managers. Unless otherwise specified, these messages will be transmitted through the default transmission queue.Ī dead letter queue is a local queue where messages that cannot be delivered are sent, either by the queue manager or an application. Special queue types can be defined, such as transmission queues and dead letter queues.Ī transmission queue is a queue that holds messages that will eventually be sent to a remote queue when a communication channel becomes available. A queue name must be unique within a queue manager. It also performs other functions associated with message queuing.Ī queue is a named destination that applications use to put and get messages. The queue manager is a system program that is responsible for maintaining the queues and ensuring that the messages in the queues reach their destination. SAS CALL Routines for the Common InterfaceĪttachment Layout for Websphere MQ and MSMQ Through Common Messaging InterfaceĪttachment Error Handling for Common Messaging Interfaceīefore you use the WebSphere MQ applications, you must create a queue manager. Using a Repository with Application Messaging TIB/Rendezvous Certified Messaging Coding Example Using TIB/Rendezvous with the Common Interface Polling Message Queues from the Object SpawnerĬonfiguring Multiple Clients To Read From a Single Queue Configuring WebSphere MQ with the WebSphere MQ Explorer

Rfhutil connection string