Spring Cloud Stream's JMS-binder implementation is under incubation. We are aiming to release a milestone shortly after Spring Cloud Stream's Chelsea.RELEASE.
With this binder implementation in the classpath, you could build apps to produce or consume from JMS based messaging middlewares.
Given the license requirements, TIBCO EMS probably require a custom implementation of this binder similar to IBM MQ or Solace - please feel free to submit a proposal and/or a pull request against JMS-binder repo.
Once we have the binder implementation, you could then directly interact with backing JMS queue/topic in Spring Cloud Data Flow via explicit-broker-destinations. You don't need a JMS source/sink application in this model; instead, you can directly publish/subscribe to named channels.