Linking Service Catalog from one instance to another

[bennyphipps]

I think I know the answer to this question but we've had a question asked by the business.

We have 2 instances in the organisation being used.  

Instance #1 - is being used for basic Service Catalog, incident, change and a few other applications

Instance #2 - used for service Catalog and Orchestration workflows (MID servers etc etc).

The business would like to use Items from Instance #2 DIRECTLY from Instance #1.

Options I would see would be:

• Direct integration using web service

        I see many problems with this regarding how do you copy variables linking to a table in another insatnce client scripts script includes in other instances etc etc etc.

• A URL link in Catalog of Instance #1 to the other instance Cat Item in Instance #2

        Users would obviously be transferred (seamlessly) to another instance. But again this would possibly require that users exist in bot instances etc etc

In both cases tracking of reqeusts woudl be a nightmare...

Obviously ONE instance would be the best option by a million miles!!!   I just want to know how difficult it would be to link instances in sucha complex way.

Regards,

Ben

[Kalaiarasan Pus]

If you need all these things, can't you just export the catalog item and use it across both the instance ?

[bennyphipps]

Well indeed... another solution would be to completely duplicate all the functionality in the one instance.

This would mean you did everything in one instance and wouldn't need to link the two together.   Otherwise you'd haev to export everything not just the cat items but a lot of other tables/scripts etc as well.

I can't see how it'd be possible to be honest

[Kalaiarasan Pus]

You would need a dummy catalog or a ui page to collect the data at instance 1 ... Hence Instead of creating a new catalog , I suggested exporting the catalog part from the other instance and have the workflow of the catalog do the integration stuff.

[jitendrakumarsa]

same required for me