Is anyone out there using TIBCO with APPIAN for messaging or any other purpose?

We're not using Appian with Tibco, but there are some general architectural patterns when it comes to using integration stacks with Appian. For asnync service calls JMS should be the technology of your choice. Speaking in Tibco Terms you would use EMS/BW to realize the integration logic. When it comes to sync integration it can either make sense to use web services or JMS request reply. Both work fine with Appian.

One interesting building block of the Tibco stack is BE for CEP. When you do CEP you have quite a few use cases where you want to start a manual process after the detection of a certain pattern. The integration to Appian should be pretty straightforward for this case as well using JMS (EMS).

Thanks a lot Moritz. But again TIBCO has its own BPM,. why would client use TIBCO and appian also right. or may be clients could have just tibco messaging license and use Appian for bpm. We use webservices as of now ,but looking into JMS as other vendor products have to be integrated.

If a client is convinced that Appian is better than the Tibco BPM product they would go for Appian. The technical integration from Appian with other Tibco products should be easy and no reason not to use Appian as the BPM layer.

Actually found out Tibco is used as service bus and no messaging/bpm. Thanks Moritz.