Configuring enterprise messaging using IBM MQ
The information here applies to software running both in Pega Cloud and on-premises applications.
Pega PlatformTM supports for asynchronous messaging integration configurations using IBM WebSphere MQ (IBM MQ). IBM MQ asynchronous messaging configurations are useful for Pega Cloud applications when REST or SOAP connectivity is not suitable for your application environment.
For asynchronous messaging integration configurations on Pega Cloud systems, Pega Cloud customers are solely responsible for any applications or software that you import into your Pega cloud environment, including libraries and requisite licenses: if you import incorrect files or unauthorized software and negatively affect your Pega Cloud environment, this can result in system downtime and require you to work with Pegasystems Global Customer Support to restore your environment.
Pega Platform has proven interoperability with the following versions of IBM MQ servers:
To configure enterprise messaging for a Pega Platform environment, it must satisfy the following conditions:
- IBM MQ servers must be available and accessible from your Pega Platform environment, and you must identify the topics and queues to use. If these servers are not available, you can create mock environments to facilitate integration with your Pega Platform application.
- The IBM MQ servers must be secure and you must configure the required authentication information for using the servers.
- You must install the appropriate Java client libraries installed onto the Pega Platform environment. As a best practice, use the latest Java client libraries for IBM MQ Version 9 and later. Verify that you import the correct JAR files and that you have all of the requisite licenses. Your system might need to be restarted for the libraries to load correctly. For more information about the Java client libraries to install, see the IBM MQ documentation.
Configuring messaging with IBM MQ
Configure connectivity to your IBM MQ server. For more information, see About MQ rules.
Ensure that your connectors are secure for the type of integration and for the data that is being transmitted. Security measures include:
Using a secure tunnel to provide data transport encryption. You can create a secure tunnel by using the following methods:
Use a VPN connection. For Pega Cloud applications, this method is available for every provisioned environment.
Use Amazon Web Services Direct Connect. This method is appropriate if you utilize dedicated carrier networks.
Encrypting your message data before transmission to the server provider.
Using strong credentials, with or without single sign-on (SSO), for confidential connections.
When you configure security for IBM MQ connectivity, select the cipher strength based on your organization's requirements.
Verify that your Pega Platform application is configured with the appropriate access groups, roles, and privileges. For more information, see Authorization models in the Pega 7 Platform.
Published February 22, 2017 — Updated August 7, 2018