MQ Server form – Completing the Environment tab

Use the Environment tab to specify information for connecting to an IBM MQ server.

Field	Description
Apply MQ bindings transport	Select to use MQ bindings transport to connect to the IBM MQ server.
Hostname	Enter the network name of the IBM 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 the TCP/IP port used for communicating with the IBM 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 IBM 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 for connecting to the IBM 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 IBM 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.
Apply TCP security settings (SSL/TLS)	Select to enable your application to send and receive queued messages securely with IBM MQ by using SSL or TLS.
Cryptographic security level (Filters IBM MQ cipher suites)	Select the category of cryptographic security standard that the system uses to filter the IBM MQ cipher suite list. A cipher suite contains the algorithms used for key exchange, hash, authentication, and cryptography. Select the type of cipher suite that provides the level of protection best suited for your requirements. All available cipher suites – Select this category to choose from all available categories of cipher suites. FIPS cipher suites – Select to use US Government standard ciphers that are used by non-military government agencies and government contractors. This category of cipher suite uses the Data Encryption Standard (FIPS 46-3) and the Advanced Encryption Standard (FIPS 197). Suite B 128-bit cipher suites – Select to use NSA Suite B Cryptography, which is used for unclassified and most classified information. This category of cipher suite uses Elliptic Curve Cryptography for key establishment and authentication algorithms, and AES as the encryption algorithm. The 128-bit security level corresponds to an elliptic curve size of 256 bits and AES-128, and uses SHA-256. Suite B 192-bit cipher suites – Select to use NSA Suite B Cryptography, but with the 192-bit security level. This security level corresponds to an elliptic curve size of 384 bits and AES-256 and uses SHA-384. Custom – Select this option to use your own cipher suite string. You might also want to save a configuration with a cipher suite that is available in an environment to which you are exporting the application, but is not available in your current development environment.
IBM MQ cipher suite	Select a cipher suite used to negotiate the security settings between the Pega Platform client and the IBM MQ server. The current run time environment that you are using for your Pega Platform may not support all of the cipher suites for your selected cryptographic security level. See the PDN article IBM MQ server support for secure message queuing Matching cipher suites correspond to cipher suites that are available in the current JRE that is installed with your Pega Platform application. If you migrate the application to a server with a different JVM, a matching cipher for the selected IBM MQ cipher suite might not be available. Non-Matching cipher suites do not have a corresponding cipher suite in the installed JRE.
Truststore	Enter or create a Truststore record that contains the IBM MQ server certificate to use in the SSL or TLS handshake.
Keystore	Optional: Enter or create a Keystore record for storing the Pega Platform client's private/public key pair that is used by the IBM MQ server to authenticate the client.
Secret key reset count (# of bytes sent/received before TLS renegotiation)	Optional: Enter the number of bytes that are sent or received within the SSL or TLS conversation before the secret key is renegotiated. Note: The default value of this field is 0, which indicates that secret keys are not renegotiated by default.
Peer name	Optional: Enter a distinguished name pattern that allows the queue manager to identify itself by using an SSL or TLS certificate. This pattern ensures that your application communicates with the correct queue manager. It should comply with validation rules defined by IBM MQ for SSLPEER values.
Test connectivity	After you complete this form and save the data instance, click to confirm that your system 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 Explore	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. Click Browse Messages to view all messages in the queue. If you have the proper role and privilege, you can perform the following actions: Add messages to the queue - click Put Messages and complete the corresponding form. Remove messages from the queue - click Remove Messages. For an example, see the PDN article How to debug MQ connectors using BROWSE, PUT and GET message operations.