Sunday, 18 December 2016

Installing JD Edwards in AWS using RDS

Ever wanted high availability with JD Edwards while using Oracle Standard Edition?  Have you looked at the complications of licencing and recovery and turned away thinking that things are too difficult.  I know that I have.

AWS RDS for oracle has changed this dilemma, making it very easy to use oracle “as a service” – carrying over your Standard edition database licences as part of Oracle Technology Foundation and creating the durability your need in your implementation.  I’m talking about a completely recoverable and highly available (well, as highly as is needed) JD Edwards implementation using power in built AWS features and functions – as well as some smart architecture.

Myriad IT have been working closely with AWS engineers to write a seamless guide to installing JD Edwards on AWS using RDS to give you all of the above and more.  We’ve created a number of reference architectures that are built on the architecture that is spelled out in the white paper.  This means that your web servers and enterprise servers are constantly up and running in alternative availability zones.  You database is running in a single AZ using RDS and will “fail over” to an alternate AZ seamlessly to JD Edwards.  JD Edwards has never been perfect at handling these fail-overs – but a quick restart of ent and we (if required) will give your complete functionality AND production scale while handling a DR event.  This power also gives you quasi high availability at the same time.

AWS have enabled you to architect a highly available and disaster recoverable JD Edwards environment facilitated by RDS.  The white paper that has been created in conjunction with AWS shows how (with a couple of tweaks) you can simply get JD Edwards running in AWS using RDS – seamlessly.  You can seem more details here https://aws.amazon.com/blogs/database/installing-jd-edwards-enterpriseone-on-amazon-rds-for-oracle/ and actually download the white paper here: https://aws.amazon.com/whitepapers/#database-applications

This shows you the exact steps for running the platform pack against RDS and using the native datapump files and utilities to get JD Edwards working in RDS.  After following the process, you’ll be able to run up your deployment server, run all of your ESU’s and get the environment complete is a very small amount of time.  You can then perform any amount of performance testing and take advantage of limitless elasticity to bring your business a very cost efficient, stable and powerful platform.

Myriad IT have taken this concept further than the white paper that you see here, we’ve implemented media objects to sit natively in S3 buckets, we are using LAMBDA functions which call AIS forms to “pre-cache” and environment on a Monday morning to take away those slow patches.  We have ELBs in front of load balanced pigeon pair web and ent servers to scale when required – and more.

If you are considering dipping your toes into the cloud, our JD Edwards reference architectures, many live clients and implementations will surely make your journey more efficient.

I’ll begin to post more technical details on the implementation of JD Edwards in AWS – in an attempt to try and highlight the efficiencies that you can gain from this implementation type.

We are so proud to be involved in this innovation with such an amazing business partner – AWS!

No comments:

Extending JDE to generative AI