Description:
The documentation refers how to setup a JMS channel and the necessary JMS transport properties. The following will aid in debugging.

1).Generally, EMS is centralized and the API Central Logger acts as a client. The client should have the necessary EMS client libraries located at ASG_HOME/ext/tpcl. (Place the file tibjms.jar or jms-2.0.jar in the location specified).

2). Confirm that all properties mentioned in the documentations are set.

3). The QueueConnectionFactory and the TopicConnectionFactory should exist with the same name as specified in the properties. Confirm that the connection factory resolves to the FQDN of the EMS server so that the client can connect to the correct server.

4). If there are still issues, set the cl cdd file from:

<log-config id="logConfig">
            <enabled>true</enabled>
            <roles>*:info</roles>

            <files>

to:

 <log-config id="logConfig">
            <enabled>true</enabled>
            <roles>*:debug</roles>
            <files>

so as to enable the DEBUG logs on restart to check why the engine does not start.

Debug Central logger issues when Central Logger is set to listen on EMS.

https://docs.tibco.com/pub/api-exchange-gateway/2.1.1/doc/html/TIB_api-exchange-gateway_users_guide/wwhelp/wwhimpl/common/html/wwhelp.htm#href=GatewayManagement.17.5.htm&single=true