• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Building integration with multiple JDE applications?

teckhoff

Member
Hello,

Wondering if anyone has some thoughts or knowledge on building an integration with multiple JDE applications?

Our company is an application that handles B2B transactions and has built integrations with multiple ecommerce platforms such as Shopify, Magento and BigCommerce. We are in the beginning stages of researching how best to do this with JDE and plan to have multiple JDE customers. We have started working with Oracle and have been discussing building it in Oracle Cloud with their JDE adapter. However, those integrations only allow 1 JDE application to be in an integration and we need to create an integration that can be used with multiple JDE applications.

Anyone have experience with this, or have some knowledge on the best design approach for this? Any help would be appreciated, thanks!
 

teckhoff

Member
Can you clarify what you mean by "1 JDE application"? Are you referring to a JDE instance?
yes, Oracle said you can only have 1 JDE instance as a trigger in the integration. So in order to use Oracle Cloud for our integration we would need to create a base integration and clone it for each JDE customer and change the JDE instance for each. Which for us is not really a sustainable model, because if we ever have to make a change to the integration we'd have to make it in the base one and re clone all of them again. So really hoping connecting directly to JDE API endpoints is a possibility, which it looks like using Business Services it is? But I'm still doing more research.
 

jdelisths

Reputable Poster
create a base integration and clone it for each JDE customer
Can you share which integration methodology are they referring to here? I am trying to grasp why it cannot be cloned.
 

teckhoff

Member
Can you share which integration methodology are they referring to here? I am trying to grasp why it cannot be cloned.
Sorry, it can be cloned. Problem we have with that is, if we ever want to make a change we'd have to make it in the base integration and then re-clone and re-configure the trigger connection for each of our JDE customers. This isn't a problem in the short term, but once we have a lot of JDE customers it would be. Also, we have to pay for each of these integrations. Whereas if we wrote our own code that could connect to JDE through APIs that would be preferable because it is one place to make changes, and have a formal code review process, etc.
 
Top