So you've made your decision to choose JD Edwards as your ERP platform, but you're unsure if a cloud deployment is right for you. It is a difficult decision with many variables and options, especially to companies where they've always kept their systems on-premises. Some may be led down the path where non-Prod (Dev/Test) servers and environments are placed on the cloud and Production is implemented on-premises, or vice versa, and all are part of a single instance of JD Edwards. This is a decision that needs to be carefully reviewed.
JD Edwards, out of the box, is written and configured so that all environments share a common database for system related information (user details, security, job queues, system definitions, and all kinds of technical configuration details). For simplicity, we'll just call this the system database. On the other hand, each JD Edwards environment also has its own distinct objects and/or data schemas, or a combination thereof. But no matter which environment a user uses, it is constantly talking to the system database, which for obvious reasons, you keep wherever your Production servers reside. So splitting out non-Prod and Prod into two separate data centers, one being the Cloud and the other being on-premise, means that the non-Prod users will need to constantly communicate with the system database at the other data center over a WAN connection. This type of setup will likely lead to very slow performance for non-Prod users. So, is there a workaround for this? Possibly, but not a simple one, and certainly not within the scope of this article.
So when does having JD Edwards Dev/Test on the cloud make sense? I can think of 2 use cases, but I'm sure there are more.
- A customer decides to implement JD Edwards but their procurement/delivery of on-premises hardware is either delayed or strategically pushed out. In this case, the implementation project can start on schedule by spinning up JD Edwards with an IaaS vendor. Oracle Cloud probably makes the most sense here, but any IaaS vendor can be employed. A detailed solution and plan to export/import data, configurations, developed objects, etc. to the on-premises JD Edwards instance will need to be strategically mapped out beforehand.
- A customer is contemplating an upgrade to JD Edwards 9.2 and wants to take it for a test drive to experience firsthand what the excitement is all about. The quickest and most efficient way would be to subscribe to Oracle Cloud and deploy the JD Edwards 9.2 templates from Oracle's Marketplace. You could take a high level test drive of the 9.2 features by going with the Trial Edition, or go with the full featured Multi-tier option if you are looking to do a deeper dive, such as retrofit analysis.