Back Forward MQ Server form
Completing the Environment tab

About MQ Server data instances

Use the Environment tab to specify how Process Commander connects to a WebSphere MQ server.

Field

Description

Host Name

Enter the network name of the WebSphere MQ server host.

This field supports the Global Resource Settings syntax (=.PageName.PropertyName). The default property name for this field is pyHostName. For more information, see Using the Global Resource Settings feature.

Port Number

Enter a TCP/IP port for communicating with the WebSphere MQ server.

This field supports the Global Resource Settings syntax (=.PageName.PropertyName). The default property name for this field is pyPortNumber. For more information, see Using the Global Resource Settings feature.

Channel

Enter the channel name on the WebSphere MQ server.

This field supports the Global Resource Settings syntax (=.PageName.PropertyName). The default property name for this field is pyChannelName. For more information, see Using the Global Resource Settings feature.

User ID

Optional. Identify an MQ user ID that Process Commander can use to connect to the WebSphere MQ server.

This field supports the Global Resource Settings syntax (=.PageName.PropertyName). The default property name for this field is pyUserID. For more information, see Using the Global Resource Settings feature.

Password

Optional. Enter a password for connecting to the WebSphere MQ server.

This field supports the Global Resource Settings syntax (=.PageName.PropertyName). The default property name for this field is pyPassword. For more information, see Using the Global Resource Settings feature.

MQ bindings transport

Select if Process Commander is to use MQ bindings transport to connect to the WebSphere MQ server.

On Windows-based servers, this setting requires the IBM-provided file mqjbnd05.dll be present and included on the system classpath.

 Test Connectivity  

After you complete this form and save the data instance, click to confirm that Process Commander can connect to the MQ server.

The system attempts to connect to the server only; no messages are processed. The system presents test results in a separate window, identifying the parameters used in the test, the steps attempted, and the outcome of each step.

MQ Explorer

Click this button to display the MQ Queue Details in a separate window.

In the MQ Explorer, choose a Queue Manager and Queue Name using the SmartPrompt. The Destination field is automatically populated. Click the Browse Messages button to view all messages in the queue.

If your production level is both lower than 5, and the logged in user has the proper Role/Privilege, you can:

  • You can add messages to the queue by clicking the Put Messages button and filling out the corresponding form.
  • You can remove messages from the queue by clicking the Remove Messages button.
For an example, see Pega Developer Network article PDNPRKB-25644 How to debug MQ connectors using BROWSE, PUT and GET message operations.

zzz About MQ Server data instances