Configuring the BusinessEvents JMS Channel for a TIBCO Cloud Messaging (TCM) EMS Service
Article ID: KB0072180
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | 6.x |
Description
This article provides guidance on configuring the BusinessEvents JMS Channel to connect to a TIBCO Cloud Messaging (TCM) EMS service. The TCM configuration file is obtained from the TCM web ui, and is used to configure the necessary JMS Channel properties. This allows you to publish/consume messages, using a locally-run (on-prem) BusinessEvents application, to/from your TCM EMS service.
Environment
TIBCO BusinessEvents and TIBCO Cloud Messaging
All Supported Platforms
Resolution
In the TCM web ui, go to the ' Authentication' screen and select ' Create Role'. Provide a Role Name, and select the EMS service. Also ensure this role is entitled to Publish and Subscribe.
When you are returned to the Authentication screen, you should now see the role you created in your role list. In the ' Configuration File' column, select the option to download the role configuration file ( tcm-config.yaml). This file contains the authentication key for this role, as well as the connection details for the TCM EMS service.
The tcm-config.yaml contains the EMS server name and port, as shown on the ' ems_server' line. Since TCM EMS requires you to make a secure SSL connection, you must obtain the EMS server's public certificate. You may do this using openssl. For example:
After obtaining the server's public certificate, point your BE application to its containing directory using the BE_GLOBAL_TRUSTED_CA_STORE Global Variable. For example:
In the above example, the EMS server's public certificate ( tcm-ems.pem) should be placed in C:/be_global_trusted/
Next, open the JMS Channel definition (or, open the *.sharedjmscon connection resource if the EMS connection is configured as a separate resource file), and set the following properties:
Your local BusinessEvents application is now configured to publish/consume messages to/from your TCM EMS service.
When you are returned to the Authentication screen, you should now see the role you created in your role list. In the ' Configuration File' column, select the option to download the role configuration file ( tcm-config.yaml). This file contains the authentication key for this role, as well as the connection details for the TCM EMS service.
The tcm-config.yaml contains the EMS server name and port, as shown on the ' ems_server' line. Since TCM EMS requires you to make a secure SSL connection, you must obtain the EMS server's public certificate. You may do this using openssl. For example:
openssl s_client -connect tib-sub-****-ems0.messaging.cloud.tibco.com:12345 </dev/null | sed -n -e '/-.BEGIN/,/-.END/ p' > tcm-ems.pem
After obtaining the server's public certificate, point your BE application to its containing directory using the BE_GLOBAL_TRUSTED_CA_STORE Global Variable. For example:
In the above example, the EMS server's public certificate ( tcm-ems.pem) should be placed in C:/be_global_trusted/
Next, open the JMS Channel definition (or, open the *.sharedjmscon connection resource if the EMS connection is configured as a separate resource file), and set the following properties:
- User Name: The value of 'ems_username' from your tcm-config.yaml.
- Password: The value of 'tcm_authentication_key' from your tcm-config.yaml.
- Provider URL: The value of 'ems_server' from your tcm-config.yaml.
Your local BusinessEvents application is now configured to publish/consume messages to/from your TCM EMS service.
Issue/Introduction
Provides the steps needed to configure the BusinessEvents JMS Channel to connect to a TIBCO Cloud Messaging (TCM) EMS Service.
Feedback
Yes
No
Powered by
