Selecteer een pagina

Move to OCI and take full advantage of the Oracle-on-Oracle application stack

As you all know Oracle Cloud Infrastructure (OCI) is a secure and scalable public cloud offering to use as a platform for your Oracle JD Edwards application. We see more and more Oracle JD Edwards customers moving to OCI, taking full advantage of the Oracle-on-Oracle application stack.

Some of the main advantages of OCI for Oracle JD Edwards customers include:

advantages of OCI for Oracle JD Edwards

Without going into too much detail on the above, we will address one of the most common questions from our customers about moving to the cloud: “What about integration with other systems, which are part of the parcel of our JD Edwards Landscape?”

A JD Edwards landscape doesn’t always exist on its own, but always has a lot of interfaces, whether that may be with CRM or Ordering systems, logistic systems, scanning systems, banks, or all kind of other systems.

Surrounding JD Edwards we see various types of integrations used:

  • (Batch) File based integration
  • Close integration with Business services (BSSV) or Real Time Events (RTE)
  • API Rest integration using AIS/Orchestrator or Cantara

(Batch) File based integration

File based integration can be easily used in OCI. Certain file locations can be made available (from your internal or external networks) so files can be stored safely and then picked up automatically.

Close integration with Business services (BSSV) or Real Time Events (RTE)

BSSV and RTE integrations require low latency integration, something that is easily accessible with OCI. It is even possible to have services spread across multiple Availability Domains (AD) (an AD is part of a region; a Region can have 3 AD’s linked with very low latency, ensuring high availability since every AD is a DC on its own).

API Rest integration using AIS/Orchestrator or Cantara

Nowadays most SaaS solutions use API/Rest integrations. Integrations with Microsoft CRM, Salesforce, Oracle CPQ, Oracle Supply chain, open up the right ports to other systems so that API integration can be enabled in a secure way. This can be done over the internal network or also over the internet when and where possible.

As you can see, integrations can be easily realised and executed in more or less the same that you were previously used too.

Furthermore, OCI has the ability to segment your networks in a very secure way reducing the risk on opening your system up too much to the outside world.

For data transfer in OCI, Oracle doesn’t charge additional costs, however for data transfer outside of OCI there is a 10 GB per month data limit if you use VPN connections. If you make use of Oracle Fast Connect there is unlimited in and out data transfer possible (of course within reasonable limits).

If your organisation uses Microsoft Azure you can save data transfer costs when taking advantages of the OCI – Azure interconnect.

Over the last few years, we have supported various customers on designing their JD Edwards landscape on OCI, taking into account: security, licensing, integrations, availability and costs. We can estimate your running costs in OCI closely, so you won’t encounter any unpleasant surprises when you move to OCI.  After the support, moving onto designing, we can assist in planning and executing the migration project whether it is a 30 or 3000 user environment. Every customer is different and has specific and unique objective points which we will address throughout our design phase.

Are you ready to start considering moving JD Edwards to the Oracle Cloud? Contact us and let’s begin your journey!

Do you have any questions or doubts? Please let us know.


12 + 7 =