Ebonding 2 Servicenow instances

[rwagner]

Hey there everyone... I have a question regarding Ebonding.

Are there any tutorials on how to Ebond 2 separate instances of Servicenow? I have a q request from a client to Ebond our Servicenow deployments.

Thanks!

[Sashi K1]

Hi

If eBond is for deployment how about using ServiceNow Team Development? Which could connect multiple ServiceNow Instances from one Hub instance and makes your deployment seamless.

http://wiki.servicenow.com/index.php?title=Team_Development#gsc.tab=0

In addition to that from Helsinki ServiceNow introducing Development Studio. Which allows SN instance to be Integrated with a source control system GIT within clients network. Which helps to baseline code and centrally deploy across instances using Team Development Plugin.

If you are looking for normal deploying update sets across instances, its same like using Update Source configuration and pull update sets between instnaces

Thanks

Sashi

[Danny Mortense1]

If you are asking more about a B2B type scenario where you wish to transfer transactions from one instance over to another, then Web Services might be the answer you are looking for.

For example, if you have a business customer using ServiceNow and your company is using ServiceNow, can you send transactions such as incidents from the customer instance and have these logged automatically into your company instance? Yes you can.

This is useful if the customer has an issue with something you support. Rather than logging the incident in their own system and you system, they can do it once and have the business logic take care of the rest.

This can easily be done by opening your tables up to SOAP or REST and allow the customer incident to post records into your instance.

This is actually very easy to achieve technically.

[Tom Laciano]

Danny,

Are you able to share a reference for configuring SOAP or REST?

Regards

Tom

[ben_nuttin]

You could use SOAP or REST web services to e-bond the two instances, but that will run you into a few issues:

1) You might take a performance hit on one or both instances when the data sharing occurs

2) You have to maintain end points, transform maps, import set tables, etc. - the "plumbing", if you will...

3) Your sys_id's will NOT be preserved from instance to instance (which can cause headaches, for example for CMDB data or user/ group data)

My company actually provides a tool we call Replicator, which is a native ServiceNow app (installed via an update set) which allows you to e-bond two ServiceNow instances with just a handful of configuration screens (leveraging a message broker service, which handles the "plumbing" of getting data from point A to point B).

I didn't mean to be pushy, but since this is a specific use case we address, I wanted to make sure you're aware. Direct-message me if you would like more info.