IBM MQ Connection Details

The IBM MQ Connection dialog box contains the following fields:
Field	Description
Connection Name	Enter the name of the connection. This is only a label and does not reflect the name of the server.
Description	Enter a brief description.
Connection type	Select any one of the following types of MQ Connection bindings. Remote: For remote connection CCDT: For Client Channel Definition Table connection
CCDT URL Type	When using the Client Channel Definition Table, enter the URL of the CCDT file that is exported by the server to which you are trying to connect. This file is located in the queue manager home directory in the `@ipcc/AMQCLCHL.TAB` file. Refer to this file from this location or copy it to a location where it is accessible. This URL supports the HTTP and FTP protocols. Select any of the following types of CCDT URLs. CCDT-File: To select the CCDT file from local system CCDT-URL-Auth: To use the authenticated FTP or HTTP connection for the CCDT file CCDT-URL-NonAuth: To use the unauthenticated FTP or HTTP connection for the CCDT file Note: For enhanced security of the FTP or HTTP connections, do not provide credentials in CCDT URL; instead, provide the credentials in the CCDT URL User Name and CCDT URL Password fields.
CCDT File	Select the `AMQCLCHL.TAB` file from its location. It accepts CCDT file in .TAB or .tab format.
CCDT URL	Enter the URL for the CCDT file in FTP or HTTP format. Note: For security purposes, do not provide server credentials in CCDT URL.
CCDT URL User Name	The username of the user for a secure FTP or HTTP connection.
CCDT URL Password	The password is associated with the CCDT URL username for the FTP or HTTP connection.
Queue Manager Name	Enter the name of the queue manager as it appears in the start and stop commands. For example, the name of the queue manager can be QMA.
Host Name	Enter the hostname or an IP address of the machine on which the queue manager is running.
Port	Enter the port on which the queue manager TCP listener is listening. The default is 1414.
Server Connection Channel Name	Enter the name of the server connection channel.
User Name	Enter the username.
Password	Enter the password. This password is stored in an encrypted form.
Encryption Mode	Select any one of the following types of security: None: For a plain text connection. TLS-ServerAuth: For an encrypted connection where the identity of the server is authenticated. TLS-MutualAuth: For an encrypted connection where both the client and the server authenticate each other.
Keystore	Select the file containing the IBM kdb encoded keystore. This keystore is read into the configuration data of the applications and used at the runtime at the location where it is deployed. The deployment environment doesn't need to have access to this file. Note: Ensure that the keystore must contain the CA certificate for the server to connect in TLS-ServerAuth mode and an identity certificate for the client to connect in TLS-MutualAuth mode. The client certificate must be signed with a CA certificate, trusted by the server.
Keystore Stashfile	Select the stash file for the above keystore. The stash file is required so that the MQ client can open the password protected keystore. The stashfile is stored in the application configuration data.
CipherSpec	Enter the cipher specification for the server connection channel to which the application connects. You can get the cipher specification from the SSL tab of the server connection channel in MQExplorer or your MQ administrator.

Connection Name

Enter the name of the connection. This is only a label and does not reflect the name of the server.

Description

Enter a brief description.

Connection type

Select any one of the following types of MQ Connection bindings.
Remote: For remote connection
CCDT: For Client Channel Definition Table connection

CCDT URL Type

When using the Client Channel Definition Table, enter the URL of the CCDT file that is exported by the server to which you are trying to connect. This file is located in the queue manager home directory in the @ipcc/AMQCLCHL.TAB file. Refer to this file from this location or copy it to a location where it is accessible. This URL supports the HTTP and FTP protocols.

Select any of the following types of CCDT URLs.

CCDT-File: To select the CCDT file from local system

CCDT-URL-Auth: To use the authenticated FTP or HTTP connection for the CCDT file

CCDT-URL-NonAuth: To use the unauthenticated FTP or HTTP connection for the CCDT file

Note: For enhanced security of the FTP or HTTP connections, do not provide credentials in CCDT URL; instead, provide the credentials in the CCDT URL User Name and CCDT URL Password fields.

CCDT File

Select the AMQCLCHL.TAB file from its location. It accepts CCDT file in .TAB or .tab format.

CCDT URL

Enter the URL for the CCDT file in FTP or HTTP format.

Note: For security purposes, do not provide server credentials in CCDT URL.

CCDT URL User Name

The username of the user for a secure FTP or HTTP connection.

CCDT URL Password

The password is associated with the CCDT URL username for the FTP or HTTP connection.

Queue Manager Name

Enter the name of the queue manager as it appears in the start and stop commands. For example, the name of the queue manager can be QMA.

Host Name

Enter the hostname or an IP address of the machine on which the queue manager is running.

Port

Enter the port on which the queue manager TCP listener is listening. The default is 1414.

Server Connection Channel Name

Enter the name of the server connection channel.

User Name

Enter the username.

Password

Enter the password. This password is stored in an encrypted form.

Encryption Mode

Select any one of the following types of security:

None: For a plain text connection.

TLS-ServerAuth: For an encrypted connection where the identity of the server is authenticated.

TLS-MutualAuth: For an encrypted connection where both the client and the server authenticate each other.

Keystore

Select the file containing the IBM kdb encoded keystore. This keystore is read into the configuration data of the applications and used at the runtime at the location where it is deployed. The deployment environment doesn't need to have access to this file.

Note: Ensure that the keystore must contain the CA certificate for the server to connect in TLS-ServerAuth mode and an identity certificate for the client to connect in TLS-MutualAuth mode. The client certificate must be signed with a CA certificate, trusted by the server.

Keystore Stashfile

Select the stash file for the above keystore. The stash file is required so that the MQ client can open the password protected keystore. The stashfile is stored in the application configuration data.

CipherSpec

Enter the cipher specification for the server connection channel to which the application connects. You can get the cipher specification from the SSL tab of the server connection channel in MQExplorer or your MQ administrator.