Integration between 2 Servicenow instances for Incident, Service request modules
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2023 10:10 PM
Hello Team,
we have to setup the ebonding integration between 2 Servicenow instances( bidirectional integration for Incident and Service request), can anyone please guide me regarding the best solution we have listed below
1) we have decided to achieve this via scripted web services and outbound rest message
2) can we go for Integration hub OOB spokes for ebonding?
Please suggest what is the ideal solution 1st or 2nd.
Thank you!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2023 10:15 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2023 09:02 PM
Hello Sandeep,
Thank you for your response,
I want to know which approach is best, Can you please guide me.
Thank you!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2023 09:34 PM
Hi @PRKK ,
The approach i already shared in the link itself, just replace the Source/Target instance names with your respective instances.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2023 09:36 PM
Both solutions can work for setting up ebonding integration between two ServiceNow instances, but each has its pros and cons.
Scripted web services and outbound REST message: This solution is more customizable and can be tailored to specific business requirements. However, it requires more development effort and maintenance. You need to write scripts to handle the data transformation, error handling, authentication, and other aspects of the integration.
Integration Hub OOB spokes for ebonding: This solution is more out-of-the-box and requires less development effort and maintenance. Integration Hub provides pre-built spokes for various third-party integrations, including ebonding. These spokes come with standard features, such as data mapping, transformation, error handling, and authentication. However, Integration Hub is a licensed product, and you need to purchase it separately if you don't already have it.
So, the ideal solution depends on your specific requirements and constraints. If you have the development skills and want more customization, then you can go for the first solution. If you want to save development effort and have Integration Hub already, then you can go for the second solution.