Guidance for Oracle's JD Edwards EnterpriseOne with AWS Elastic Disaster Recovery
Overview
How it works
These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.
Additional considerations
Disaster Recovery Planning
AWS provides four core disaster recovery architecture patterns: Backup & Restore, Pilot Light, Warm Standby, and Multi-site Active/Active. This guidance focuses on setup, configuration, and optimization by using the Pilot Light strategy. This strategy helps you create a lower-cost disaster recovery environment where you initially provision a replication server for replicating data from the source database, and you provision the actual database server only when you start a disaster recovery drill or recovery. This strategy removes the expense of maintaining a database server in the disaster recovery Region. Instead, you pay for a smaller Amazon EC2 instance that serves as a replication server.
Application Specific Guidance
Oracle's JD Edwards EnterpriseOne is an integrated enterprise resource planning (ERP) software for midsize to large companies in a wide range of industries. A typical JD Edwards EnterpriseOne application deployment runs on an Oracle Database or Microsoft SQL Server with a supported database. This application should include all JD Edwards EnterpriseOne base components (Enterprise Server, HTML Server, and Database Server) installed in one AWS Region. We recommend the following configurations to support disaster recovery:
- Move PrintQueue into the database.
- Move MediaObjects into the database.
- Exclude the logs and temp folder from batch and logic servers.
- Exclude the temp folder from Oracle WebLogic.
- Create scripts for startup after the failover.
- Exclude the tempdb for SQL Server.
- Exclude the temp file for Oracle.
Automation and Scale
When you perform disaster recovery at scale, the JD Edwards EnterpriseOne servers will have dependencies on other servers in the environment. For example, the JD Edwards EnterpriseOne application servers that connect to a JD Edwards EnterpriseOne supported database on boot have dependencies on that database. JD Edwards EnterpriseOne servers that require authentication and need to connect to a domain controller on boot, start services that have dependencies on the domain controller. For this reason, we recommend that you automate failover tasks. For example, you can use AWS Lambda or AWS Step Functions to automate the JD Edwards EnterpriseOne startup scripts and load balancer changes to automate the end-to-end failover process. For more information, refer to Creating a scalable disaster recovery plan with AWS Elastic Disaster Recovery.
Related content
Set up disaster recovery for Oracle's JD Edwards EnterpriseOne with AWS Elastic Disaster Recovery
This prescriptive guidance outlines how you can use AWS Elastic Disaster Recovery as a disaster recovery option for your JD Edwards EnterpriseOne applications.
Disclaimer
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages