Connection details properties
You can view and set properties for connections in the Connection Details properties dialog.
To view connection details properties, right-click on the queue manager, select Connection details, and then click Properties. The following tables list all the properties that you can set:
General page
The following table lists the properties that you can set on the General page of the Connection Details properties dialog.
Item | Description |
---|---|
Queue manager name | Read-only. The name of the local queue manager. |
Connection type | Read-only. The type of connection. The three possible values are:
|
Connection name | Read-only. The connection name that is associated with the channel that owns the handle. If no channel is associated with the handle, this value is empty. This value is shown only when the handle belongs to the channel initiator. |
Channel name | Read-only. The name of the channel definition. |
Refresh interval (seconds) | The frequency with which IBM® MQ Explorer refreshes its information about the queue manager. |
Autoreconnect | The configuration of the connection to each queue manager so that IBM MQ Explorer automatically connects to it at startup or reconnects
to it if the connection is lost; for example, if the network connection to a remote queue manager
fails. Important: You can enable either the
Autoreconnect property, or the Prompt for password
property, described on the Userid page, but not
both.
|
Wait interval | The number of seconds that IBM MQ Explorer waits for messages on the reply queue. |
Expiry interval | The number of seconds that messages remain on the reply queue. This queue is the one that IBM MQ Explorer is using to communicate with the queue manager. |
Security exit page
The following table lists the properties that you can set on the Security exit page of the Connection Details properties dialog.
Item | Description |
---|---|
Exit name | Specifies the name of the exit program to be
run by the security exit. Exit name can be up
to 1024 characters long and is case sensitive. Exit name can
be a fully qualified java class name found in the directory or jar
file. Exit name can be a C exit, of the format: dll_name(function_name) .
The default path for exits is always used to locate C exits, you cannot
specify the location of the exit library in this entry field unless
no default path is set. |
in directory | Specifies the directory for the security exit (Java™ exits only). |
in jar | Specifies the jar file for the security exit (Java exits only). |
Exit data | Exit data can be up to 32 characters long. If no value has been defined for that attribute, this field is all blanks. |
Userid page
The following table lists the properties that you can set on the Userid page of the Connection Details properties dialog.
Item | Description |
---|---|
Enable user identification | Select Enable user identification to enable the fields on this dialog. |
User identification compatibility Mode | When selected, the userid and password are passed to the server in a way compatible with security exits created prior to IBM MQ 8.0. |
Userid | The userid and password, when specified, are passed to the server, and can be
used either by:
|
No password | When selected, no password is passed to the server with the userid. |
Prompt for password | When selected, the user is prompted for a password that is passed to the
server with the userid. The prompting occurs as part of the connect operation. Important: You can enable either the Prompt for password property, or the
Autoreconnect property, described on the General page, but not both.
|
Use saved password | When selected, the saved password is passed to the server with the userid. |
Saved password | The saved password to be passed to the server with the userid. |
SSL key repositories page
The following table lists the properties that you can set on the SSL key repositories page of the Connection Details properties dialog.
Item | Description |
---|---|
Trusted Certificate Store | The location of the truststore on the computer. In the Trusted Certificate Store field, browse for the location of the truststore on the computer. The truststore and keystore contain the TLS certificates that are used with connections that use client channel definition tables. It is possible that the truststore and keystore are in the same location on your computer. |
Personal Certificate Store | The location of the truststore on the computer. In the Personal Certificate Store field, browse for the location of the keystore on the computer. |
For more information about configuring IBM MQ Explorer with the default location and password of the TLS certificate store, see Specifying the default location and default password of TLS certificates.
SSL options page
The following table lists the properties that you can set on the SSL options page page of the Connection Details properties dialog.
Item | Description |
---|---|
SSL FIPS required | Read-only. If set to No (the default), any available cipher suite can be used. If set to Yes, then only FIPS-certified cipher suites can be used. |
SSL CipherSpec | The SSL CipherSpec identifies the combination of encryption algorithm and hash function that is used by a TLS connection. A CipherSpec forms part of a cipher suite, which identifies the key exchange and authentication mechanism and the encryption and hash function algorithms. The size of the key that is used during the TLS handshake can depend on the digital certificate you use, but some of the CipherSpecs supported by IBM MQ include a specification of the handshake key size. Larger handshake key sizes provide stronger authentication. With smaller key sizes, the handshake is faster. |
SSL reset count | The number of bytes, 0 - 999 999 999, that are sent and received within a TLS conversation before the secret key is renegotiated. A value of 0 means that the secret key is never renegotiated. The number of bytes includes control information that is sent by the message channel agent (MCA). If the value of this property is greater than 0 and the value of the Heartbeat interval property in the Channel properties is greater than 0, the secret key is also renegotiated before message data is sent or received following a channel heartbeat. |
Peer name | The Distinguished Name (DN) of the queue manager to be used by TLS. The peer name is set to indicate that connections are allowed only where the server is successfully authenticated as a specific DN. |