Presentation on theme: "High Availability Options for JD Edwards EnterpriseOne Shawn Scanlon, GSI."— Presentation transcript:
High Availability Options for JD Edwards EnterpriseOne Shawn Scanlon, GSI
*** Disclaimer *** Due to the technical nature of this topic, time constraints, and various experience levels in the audience, the concepts and terminology presented here will be discussed at a higher level The information presented here is based on GSI’s experiences. These slides are not intended to present ALL the high availability options, just some of the most common. The only way to really decide on the right option(s) for your company is to conduct an internal Proof of Concept (POC) and document failover behavior and times.
Agenda What is “High Availability” for E1? The E1 Logical Layers What is E1 Virtualization? What is a Content Switch? What is Active-Passive? Active-Passive Advantages / Challenges What is Active-Active? Active-Active Advantages / Challenges High Avail Options for E1 Logical Layers LIVE High Availability Architectures What is the Right Option for Me? Questions
What is “High Availability” for E1? “High Availability” for JD Edwards EnterpriseOne is usually a single site implementation that has multiple redundant servers configured at each layer in either an ACTIVE-PASSIVE or ACTIVE- ACTIVE mode to minimize planned and unplanned downtime *** High Availability with multiple sites is usually defined of as “Business Continuity”…which is whole presentation in itself.
Active-Passive Advantages Can provide automatic failover in minutes Can allow enough time to review the cause of the failure and state of “in flight” transactions –Depends on your internal Service Level Agreement (SLA) Sometimes less expensive than Active- Active with regards to hardware –Depends on if content switches are already in place
Active-Passive Challenges Manual procedures need to be in place to make sure end users VERIFY state of “in flight” transactions –Failure behavior is not the same for all E1 Apps Depending on configuration, can require a SLA with multiple hours of downtime –How long do you want to spend analyzing the failure and status of the “in flight” transactions? In some cases, dependent on tech staff being available to make manual switch –INI files Does not LOAD BALANCE end users Does not SCALE 100% of end users will be DOWN until users are re-routed to an ONLINE server
Active-Active Advantages Automatic re-route to ONLINE server(s) in a matter of seconds Allows LOAD BALANCING of end users Very SCALABLE If configured with LOAD BALANCE option, only ~50% of end users will be DOWN during failure Minimal or No Maintenance Window required –If architected properly, design will allow for maintenance to occur on half the system while the other half supports the end users
Active-Active Challenges Manual procedures need to be in place to make sure end users VERIFY state of “in flight” transactions –Failure behavior is not the same for all E1 Apps If content switches are not in house, will be more expensive to implement than Active-Passive Need Network Engineer with Content Switch experience –Need to implement scripts for fail-over / load balancing In regards to E1, the number of users might be balanced across servers, but that does not mean the servers are “load balanced” –Some E1 Apps are “heavier” than others and require more processing power / memory (e.g., Inquiry vs. Order Entry) –Need to test different algorithms to find the right one for your situation…round robin, least connections, weighting, etc.
E1 HTTP Layer Options Active-Passive –Multiple HTTP servers with manual redirection Instruct users to enter a different URL Create multiple icons on desktop to point to different URLs Active-Active –Multiple HTTP servers connected to Content Switch Develop scripts to automatically route users to an online server
High Availability Options for… E1 Presentation Layer
E1 Presentation Layer Options Active-Passive –Multiple JVMs on different ports/servers Manually change URL to an online port Create multiple icons on desktop to point to the different ports –Double-Take Software (Partners Data Systems) –E1 Virtualization (manual move) Active-Active –WebSphere Clustering with Network Deployment Mgr –Content Switch with E1 Virtualization
High Availability Options for… E1 Application / Batch Layer
What is the Right Option for Me? What is your stated SLA? Hours or minutes? How much money does your company lose for every hour the system is down? Will the end user community accept multiple hours of unplanned downtime? Is there a high political cost tied to downtime / user perception? Do you have the skills in house? Do you have the budget to procure additional hardware / software? Do you have the time to conduct a POC, implement and THOROUGHLY test?
Summary What is “High Availability” for E1? Think in Layers E1 Virtualization Content Switch Active-Passive, Active-Active High Avail Options for E1 Layers LIVE High Availability Architectures