Blue-Green Deployment of JD Edwards Enterpriseone Tools

Blue-Green Deployment of JD Edwards EnterpriseOne Tools

PURPOSE STATEMENT This document provides an overview of Blue Green deployment and how this can be leveraged in the JD Edwards system for Tools deployment.

DISCLAIMER This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software license and service agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.

Table of Contents

Overview: Blue-Green Deployment of JD Edwards EnterpriseOne Tools ...... 3 Architecture: Environment Configuration with Load Balancer ...... 4 How does it work? ...... 5

OVERVIEW : BLUE-GREEN DEPLOYMENT OF JD EDWARDS ENTERPRISE ONE TOOLS

Blue-Green deployment is a continuous delivery process that reduces risk and downtime during JD Edwards EnterpriseOne Tools deployment by running two identical environments called Blue and Green with a load balancer. Blue-Green deployment paves the way for High Availability (HA) with almost zero downtime and outages during Tools deployment. At a given time, only one environment is live. A Load Balancer is used for routing the traffic between the Blue and Green environments. Any regression issues with build after the Tools deployment can be easily resolved immediately by rolling back to the previous version by using Load balancer. This capability also enables our customers to stay current by easily adopting all the latest Tools releases.

Does your system require an outage or downtime for every JD Edwards EnterpriseOne Tools Deployment? The JD Edwards Development and DevOps teams designed the Blue-Green deployment model that ensures High Availability (HA) of the system with zero downtime and outages during EnterpriseOne Tools deployment. Blue-Green deployment with a Load Balancer is the best approach to ensure high availability and stability of the system. Deployment is one of the most important phases of the software development lifecycle, therefore all the associated activities should thoroughly be researched and tested to ensure that they are a perfect fit for your system architecture and business.

Existing Challenges

• Downtimes during JD Edwards Enterprise One Tools Deployment • Interruptions and outages if roll back to an older version is required due to regression issues with the build • The reluctance of users to stay current by adopting all the JD Edwards EnterpriseOne Tools updates, considering the overheads and interruptions to the production system during an update process

ARCHITECTURE— ENVIRONMENT CONFIGURATION WITH LOAD BALANCER

The below diagram shows how the traffic is directed between the Blue and Green environment using the load balancer.

End User Blue Environment

Green Environment

• Blue and Green are identical sets of environments, of which one will be active and the other in standby mode. • A load balancer to route the traffic between the Blue and the Green Environment. In our case, we used Oracle Traffic Director as the Load Balancer. • The database is common for both environments.

How does it work?

• The Blue - Green deployment process uses two identical environments - Blue and Green. Only one environment is active at a time, serving all the traffic with the load balancer and the other environment is in the standby mode. For this example, let us consider that Blue is in standby and Green is active. • Any new Tools Deployment or patch updates are applied to the Blue environment. • When the updates are completed in the Blue environment, you can use the load balancer to switch the traffic to the Blue environment. • In case of any regression or build issues in the updated Blue environment, you can immediately roll back and switch to the previous version on the Green environment using the load balancer.

Switching Process from Green to Blue Environment Typically, the Blue environment is promoted first. After successful testing of the Blue environment, the switch is made. The following actions are performed during the switch: • Test and health checks are performed for all the components of the Blue environment. • Users are notified about the switching process and possible active session timeouts. • All user changes and modifications are synchronized to the JAS, AIS, and Enterprise components of the Blue environment from the Green environment. • Traffic is diverted and directed to the Blue environment using the Load balancer. • Health checks are performed for all the components of the currently active Blue environment with traffic. • Users are notified about the completion of the switching process.