- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2024 05:25 AM
Hi everyone, I am integrating ServiceNow with Oracle EBS using the Oracle EBS Spoke plugin and have reached a step requiring a specific URL for HTTP(s) connection configuration. I'm unclear on how to identify or construct this URL.
Summary of the Situation:
- Goal: Integrate Oracle EBS with ServiceNow via the Oracle EBS Spoke.
- Current State: Oracle EBS instance is running on Oracle Cloud Infrastructure with a public IP address. SSH access is functional, but HTTPS connectivity for integration has been unsuccessful.
- Issue: Uncertain if the URL should be based on the public IP, an FQDN, or another endpoint. Attempts to use the public IP have failed, despite configured HTTP/S traffic in networking and security lists.
Questions:
- What URL format should I use for Oracle EBS in the ServiceNow Spoke configuration?
- Is there a best practice for identifying or building this URL?
Any guidance, advice, or shared experiences regarding setting up this integration and resolving URL configuration issues would be immensely helpful.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-02-2025 11:02 AM
From what I realized when the POC for this project was still being developed: there is no way to configure the Spoke plugin to work with oracle ebs today if you use a cloud infrastructure on the Oracle side instead of deploy your own local solution on your own server.
If you download the local bussiness suite (which is what we were interested in) and installed it into a server, then the address of this server should be used for the Spoke plugin and any http interactions in general.
At least, I think so, because we never really did this, the project was frozen.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-01-2025 10:53 PM
I would love to see some reply to this post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-02-2025 10:52 AM
Me too)))
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-02-2025 11:02 AM
From what I realized when the POC for this project was still being developed: there is no way to configure the Spoke plugin to work with oracle ebs today if you use a cloud infrastructure on the Oracle side instead of deploy your own local solution on your own server.
If you download the local bussiness suite (which is what we were interested in) and installed it into a server, then the address of this server should be used for the Spoke plugin and any http interactions in general.
At least, I think so, because we never really did this, the project was frozen.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-02-2025 08:41 PM
Thank you for sharing your thoughts. We're also in the early stages of evaluating ServiceNow for our organization. Like you, we have a significant Oracle EBS deployment, with HCM partially migrated to the Fusion Cloud. I understand the challenges that come with custom EBS implementations and the lack of out-of-the-box integration options.
I’d love to hear about the best practices and methods to connect ServiceNow with Oracle EBS. Specifically:
- Have you explored the use of the ServiceNow IntegrationHub with Oracle EBS? If so, what has been your experience?
- Would leveraging APIs, custom middleware, or third-party integration tools (e.g., MuleSoft or Dell Boomi) provide a more streamlined solution?
- How do you handle challenges like data consistency and real-time updates between the two systems?
- Has anyone leveraged Oracle APEX for connecting ServiceNow’s cloud services? If so, what was the approach and how effective was it?
Your insights on these points would be invaluable, especially as we navigate this complex integration landscape.
Looking forward to the community's advice and experiences!