When the TIBCO® Messaging Manager 3.1.1 is first tried by customers, We need to make sure we read the following documents first - this is very important:

https://docs.tibco.com/products/tibco-messaging-manager-3-1-1
https://docs.tibco.com/pub/msgmx/3.1.1/doc/pdf/TIB_msgmx_3.1.1_user-guide.pdf?id=4

If using EMS read as well:
https://docs.tibco.com/pub/msgmx/3.1.1/doc/pdf/TIB_msgmx_3.1.1_EmsCommandRef.pdf?id=3
If using Kafka
https://docs.tibco.com/pub/msgmx/3.1.1/doc/pdf/TIB_msgmx_3.1.1_AkdCommandRef.pdf?id=1
If using Pulsar
https://docs.tibco.com/pub/msgmx/3.1.1/doc/pdf/TIB_msgmx_3.1.1_ApdCommandRef.pdf?id=2

For Managing EMS, in particular, we have found the following problems

Error
HTTPConnectionPool(host='localhost', port=25241): Read timed out. (read timeout=30)

Please make sure of the following:

Requirements
To run MSGMX EMS commands, your systems need to meet the following requirements:

1_You need EMS 10.1.0 or later installed and accessible from the MSGMX server. See the TIBCO Enterprise Message Service™ Installation Guide.
2_Java must be 1.8.0_311 or later.
3_MSGMX requires that the EMS server uses a JSON configuration file - cant use an EMS that is using .conf files
4_Set the EMS_HOME environmental variable - Linux and macOS example: export EMS_HOME=/opt/tibco/ems/10.1 Windows example: set EMS_HOME=C:\tibco\ems\10.1
5_Make sure all EMS libraries are set on the CLASSPATH environmental variable, all .jar files from /opt/tibco/ems/10.1/lib/




 

When running the TIBCO Messaging Manager 3.1.1 customer may encounter issues while running the product

All