- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2017 12:36 PM
We have a customer that has made an investment in TIBCO. They are using ServiceNow but have not done any integrations. We are now planning to do integrations and I've been explaining to them some basic concepts, including the cloud/on-premise communication through a MID-SERVER. From there, they jumped to ... can we integrate SN with TIBCO. This is a GOV customer and so getting ATOs (that's Authority To Operate) is a significant endeavor and (I think) they think that because their TIBCO platform has already been ATO'd, it would make the paperwork part of the easier.
I HAVE done SN integrations with JDBC before but I have no personal experience with TIBCO. I do understand middleware/JMS broker applications, but I'm not really sure their desire to use TIBCO and a replacement for the MIDSERVER is really the right thing to do (at least to start with).
My gut is telling me to stick with what ServiceNow provides Out-of-the-Box (i.e. do our integrations using the MIDSERVER) and then later see if we can replace it with a TIBCO integration.
Looking for insights from the community here.
Has anyone done something similar (i.e. integrated SN/TIBCO where TIBCO was the MIDSERVER replacement and the on-premise middleware message brokering component)?
Ty
Solved! Go to Solution.
- 3,592 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2019 05:09 PM
Ok...we've done it! We integrated ServiceNow with TIBCO via REST. We created a REST endpoint in ServiceNow and constructed a TIBCO package to POST messages to that endpoint. I did not develop the TIBCO internals, our TIBCO expert did that, but we successfully integrated ServiceNow with a Cyber Training database using TIBCO as the middleware layer.
I must say...this is awesome! With this model in place with this customer, going forward, it will simply be a matter of exposing or creating REST endpoints on ServiceNow and configuring TIBCO to exchange information with ServiceNow on those endpoints.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2018 09:57 AM
Tibco and ServiceNow can certainly be used together. Infact, Tibco products like BusinessWorks (BW) can be used to create REST API endpoints, which could be called from ServiceNow workflows. Once Tibco creates a REST API interface, all orchestration calls from ServiceNow this can be routed through a Tibco Mashery gateway to achieve service granularity that is unprecedented.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2019 05:09 PM
Ok...we've done it! We integrated ServiceNow with TIBCO via REST. We created a REST endpoint in ServiceNow and constructed a TIBCO package to POST messages to that endpoint. I did not develop the TIBCO internals, our TIBCO expert did that, but we successfully integrated ServiceNow with a Cyber Training database using TIBCO as the middleware layer.
I must say...this is awesome! With this model in place with this customer, going forward, it will simply be a matter of exposing or creating REST endpoints on ServiceNow and configuring TIBCO to exchange information with ServiceNow on those endpoints.