Basic settings

After you create a WebSphere® MQ transport, you must configure a few basic settings associated with it.

To configure basic transport settings, click the Settings tab.

The Basic settings page of the WebSphere MQ transport.
Field Description
Host The host name or IP address of the WebSphere MQ server. When using a queue sharing group, this must be the host name or IP address of a QMGR within the group.
Queue Manager The name of the WebSphere MQ queue manager to use. On z/OS systems, this can also be the name of a queue sharing group.
Note: This field is case-sensitive.
Port The port number where WebSphere MQ is listening (the default is 1414).
Channel The name of the WebSphere MQ communication channel that is used for sending and receiving.
Note:
  • This name must be a Server Connection type because HCL OneTest™ API is a client application.
  • This field is case-sensitive.
Username The ID of the user who is sending or receiving messages from HCL OneTest™ API.
Important: Credentials in HCL OneTest™ API might or might not be used. Whether the credentials are used depends on the version of WebSphere MQ that you are using and how you configured the WebSphere MQ queue manager. For more information about queue manager authentication, see Connection authentication.
Password The password (if required) associated with the user name specified.
Application Name The value that is used to set the Put application name attribute on messages sent by HCL OneTest™ API.
Note: The value that is entered in this field is ignored unless the transport's Write Options include the following details:
  • The MQOO_SET_ALL_CONTEXT flag for Queue Open.
  • The MQPMO_SET_ALL_CONTEXT flag for Put Message.
For more information, see MQ transport: Read, Write and Browse queue settings and Configuring WebSphere MQ transports.
The maximum length of the name is 28 characters; any additional characters that you enter are truncated. The default value is "HCL OneTest™ API".
Application Type The type of connection to the queue manager.
Connection Management
To control how HCL OneTest™ API handles the connections to WebSphere MQ resources, select any of the following options by using the slider:
  • Minimize Resources. Use this option if you run sequential tests. This option maintains a few core connections, creates more connections when required, and closes them as soon as they are used.
  • Balanced. Use this option if you run a few stubs or parallel tests. This option maintains a slightly larger number of core connections, creates more connections when required, and closes them after a short period of inactivity. The queue handles are held for a short period and reused, if possible. This option is the default and all the transports that were created in HCL OneTest™ API earlier than version 8.7.1 are set to use this option.
  • Maximize Performance. Use this option if you virtualize many services. This option is similar to the Balanced settings but the connections and the queue handles are held for longer duration before closing.
Properties A collection of properties to use when you define the connection. For each property specify the property name, type, and value.
Important:
  • Property names are case-sensitive. For example, CCSID works, but ccsid does not.
  • The property type must match that of the property selected. If you are unsure as to which property type to select, use String.
  • To authenticate from a Java client to the WebSphere MQ queue manager where you want to specify a password length that is greater than 12 characters, you must add the Use MQCSP authentication property and set its value to true. For more information about this property, see Connection authentication with the Java client.

    If you fail to use this property when a password length is greater than 12 characters, authentication from a Java client to the WebSphere MQ queue manager will fail.

Feedback