How would I go about connecting two instances with one service portal?

[pablobeck]

We have two production instances serving two different use cases, and one instance hosts the service portal used corporate wide. We'd like to connect the two instances so that users can see their requests in one place. How would you recommend we go about interfacing two instances together? (i.e. user can see their RITMs in one list widget and when they drill down to record displays data for respective instance).  

[ChrisBurks]

If I understand this correctly your company has two separate ServiceNow instances for example something like companyProducts.service-now.com and companyCorp.service-now.com (just examples to make it clear).

The Corp instance hosts the Service Portal with which catalog items will be accessible through. However, your Products instance also has catalog items that should also be accessible through the Corp Service Portal.

If all that is correct, is there an issue using web services and a service portal widget on the Corp instance to connect and pull from the Table API (to get Request/RITM) and Service Catalog API (for catalog interaction) of the Products instance. 

For search capabilities you can tie in the integration with the Service Portal Search Sources. 

Of course there will need to be some indicator to determine when a catalog item is external to the Corp so that interaction will go through the integration.

That's sort of a simplification of a process but bottom line for me would be to think of it just as if it were an integration between a different kind of system walking through what, when and how things should display or what triggers interaction between the systems.

However, if that's not what you're talking about then just ignore my post. 🙂

[Daniel Draes]

I would probably go down another route.

From the instance not running the portal I would replicate all information you want to make visible (mainly requests as I understand). These requests will than be copied to the other instance - at least with the main attributes. 

These copies will be marked as 'from other instance'. If a user clicks on any of these I would redirect the user to a minimalized portal on the second instance.

You can image this is quite complex to do.

Ideally you can go back to whoever decided to separate these to things in two instances. Why is this necessary at all? The ServiceNow platform is strong and flexible and most of our customers run only one production instance even in larger deployments.