When testing the JMS Service configuration in MFT Command Center under the Management menu > JMS Service > Configure JMS Service screen, the following error is displayed:

<<<<
...
Cannot instantiate class: com.tibco.tibjms.naming.TibjmsInitialContextFactory
...
>>>>

See the attached error screenshot "JMS_Error.PNG".

All supported environments

MFT Command Center and Internet Server do not ship any JMS Client JAR files. These JAR files must be provided by the customer and are typically located in a directory on the JMS Server. The JMS Service requires these JMS JAR files to be copied to the "<MFT_Home>/server/webapps/cfcc/WEB-INF/lib" directory.

For EMS, add the list of JMS JAR files given below to the "<MFT_Home>/server/webapps/cfcc/WEB-INF/lib" directory of the MFT Command Center and Internet Server and restart the services. This will fix this issue. 

tibjms.jar
tibcrypt.jar (SSL only)
jms-2.0.jar

The above files can be found under <EMS-Home>\lib directory.

TIBCO Managed File Transfer Command Center error "Cannot instantiate class: com.tibco.tibjms.naming.TibjmsInitialContextFactory" when configuring JMS Service