Hi Jez, hope all is well.
We are starting to look at integrating our back office applications with our Jive instance and have run into a few situations where we are not sure how to continue. I was hoping that you might be able to provide us some guidance or at least point us in the right direction on some of these questions:
1) If I want to display information on an existing Jive page, like a space or group page, what is the best way to do this? In my test group below, the spaces in red are iframes linking back to internal (behind firewall) applications:
I am not aware of any other way to display partial content on a page like this outside of an iframe, but I am getting a lot of pushback saying that Jive does not recommend the use of iframes.
What are we supposed to do here?
2) At a higher level, what should our strategy be in linking applications that are behind our firewall to Jive? Should we link directly to these systems and try to scrape out the pertinent information that we need for a specific application? Should we stick a web service in between that proxies Jive and our back office?
As an example, if I want to get a list of SharePoint sites that I have access to, currently we link straight to a page within SP that already has this logic. But we're not sure what happens when we upgrade SP. We're not sure how to handle taking SP offline for maintenance, etc. We could certainly move or replicate this functionality to a web service layer that could handle these issues, but then we incur the additional cost of building and supporting out this layer in our infrastructure.
I apologize for the wall of text, but I am not sure who else to ask. Our TAM has not been able to field developer questions nor find me a suitable contact for this area of Jive.
Any insight you might provide is massively appreciated.
ECM Senior Software Engineer
Global Technology Services
1500 Corporate Drive
Canonsburg, PA 15317