Oracle COTS Applications on AWS


Published on

In this session, we will discuss strategies, tools, and techniques for migrating and running off-the-shelf Oracle packages on AWS. We'll consider applications like Oracle eBusiness Suite, PeopleSoft, JD Edwards, Endeca, and Siebel. These applications are complex by themselves, they are frequently customized, they have many touch points on other systems in the enterprise, and they often have large associated databases. Therefore, they may not seem good candidates for the cloud at first look. Nevertheless, running enterprise applications in the cloud affords powerful benefits, and we'll identify the factors and best practices that most influence success.

Published in: Technology, Business

Oracle COTS Applications on AWS

  1. 1. •  •  •  •  •  Oracle Enterprise applications support and licensing Popular Oracle COTS on AWS Architecture Best Practices Customer Successes Roadmap and Resources
  2. 2. This timeline highlights the collaboration between Oracle and AWS along with the major milestones and joint deliverables. Oracle & AWS Oracle Secure Backup Cloud Module on Amazon EC2 Oracle on Amazon EC2 2007 2008 2008 Oracle on RDS Oracle VM virtualization support 2010 2011 Ref Arch, AMIs Oracle Test Drive 2012 2013
  3. 3. AWS is the only virtualization platform that Oracle supports. All Oracle technology and applications are support by AWS. •  Oracle technology stack supported by Oracle to run on AWS Xen or OVM •  Oracle Database and Middleware (Application Server) supported on AWS Xen •  Oracle applications are supported when they run on OVM •  Oracle Enterprise Linux (OEL) supported on AWS
  4. 4. •  All of these Oracle Products are fully supported on EC2 Oracle E-Business Suite Siebel JD Edwards EnterpriseOne Agile PLM JD Edwards World Hyperion Primavera Endeca Demantra Oracle Fusion Applications PeopleSoft Applications InQuira Oracle Hyperion ATG Web Commerce Try out many of these Enterprise Applications on AWS with Test Drive
  5. 5. "   Oracle VM is Oracle’s own hypervisor built based on XEN "   In addition to Amazon XEN hypervisor AWS also offers EC2 instances with Oracle VM (OVM) as the hypervisor. "   When an AMI based on OVM is launched, AWS automatically chooses OVM as the hypervisor for that EC2 instance. "   Oracle Software can be run in EC2 on OVM or without OVM (Amazon Xen) "   OVM based instances does not support some of the newly introduced features of AWS including "   Virtual Private Cloud (VPC) "   Cluster Compute Instances (CC) and Cluster GPU instances "   Hi I/O instance "   EBS Optimized Instances
  6. 6. "   All Oracle Software on AWS will work just fine without OVM, OVM is basically for Oracle Support. "   OVM is required for support only for Enterprise Apps not necessary for Database or Middleware. "   Many SI partners are running Oracle Enterprise Apps on EC2 as managed service. "   Running on Oracle XEN is like running Oracle Enterprise Applications on VMWare, Citrix, or Microsoft Hypervisor. These are not supported by Oracle as well. "   New Customer Accounts on “VPC by Default” will have an exception process that will allow them to run OVM instances if needed. "   Talk to your Oracle sales rep or Oracle support
  7. 7. Traditional and AWS Environments All Oracle Software licenses are fully portable to Amazon Elastic Compute Cloud (EC2) •  •  •  •  •  Enterprise License Agreement (ELA) Unlimited License Agreement (ULA) Oracle Partner Network (OPN) Business Process Outsourcing (BPO) Oracle Technology Network (OTN) Oracle on AWS •  •  Processor & Socket Licensing: •  0.25 core multiplier for standard licenses (sockets) •  0.5 core multiplier for enterprise licenses (processor) Oracle Cloud Licensing Policy
  8. 8. PeopleSoft Architecture on Amazon Highly available and scalable PeopleSoft implementation can be complex and expensive. Dense peak periods and wild swings in traffic patterns result in low utilization rates of expensive hardware. Amazon Web Services provides the reliable, scalable, secure, and high-performance infrastructure required for Oracle PeopleSoft while enabling an elastic, scale out and scale down infrastructure to match IT costs in real time as customer traffic fluctuates Sample Architecture •  High-Memory Extra Large Instance Database Server •  m1.large Application Servers •  m1.small Web Servers •  m1.medium File and Batch Servers Developed by
  9. 9. PeopleSoft Architecture on Amazon The user's DNS requests are served by Amazon Route 53, a highly available Domain Name System (DNS) service. Network traffic is routed to infrastructure running in Amazon Web Services. HTTP requests are first handled by Elastic Load Balancing, which automatically distributes incoming application traffic across multiple Amazon Elastic Compute Cloud (EC2) instances across Availability Zones (AZs). It enables even greater fault tolerance in your applications, seamlessly providing the amount of load balancing capacity needed in response to incoming application traffic. Developed by
  10. 10. PeopleSoft Architecture on Amazon Oracle Web, application and database servers are deployed on Amazon EC2 instances. These are Amazon Machine Image (AMI) using Oracle Enterprise Linux 5.3 and Oracle PeopleSoft Amazon Spot Instances or Auto Scaling can be used to support batch processing. Web and application servers are deployed in an Auto Scaling group. Auto Scaling automatically adjusts your capacity according to conditions you define. This ensures that the number of Amazon EC2 instances increases seamlessly during demand spikes. Oracle Database 11g is run on RDS Instances and replicated using RDS replications. Oracle database backups and the batch flat files for integration with the corporate data center are stored on Amazon Simple Storage Service (S3), a highly durable storage infrastructure designed for mission-critical and primary storage. Developed by
  11. 11. PeopleSoft Architecture on Amazon Availability zones (AZs) are distinct geographic locations that are engineered to insulate against failures in other AZs. Multiple AZs are combined into a region. Here, the entire web application is deployed in two different AZs for high availability. Developed by
  12. 12. Project Overview Approach to Moving to AWS •  Setup VPC •  Create Foundational infrastructure (Web, App, Proc, DB Servers) •  Copy Database Into AWS •  Complete Configuration •  Test Environment and Application •  Test Move to Production (2 Iterations Min) •  Move to Production Total Time to Deploy – 6-12 Weeks Developed by
  13. 13. •  Fixed  infrastructure  that  is  o1en  over  or  underu3lized   •  Produc3on  -­‐  Varying  Demands     –  Based  on  line  of  business  demand  may  vary     •  •  •  •  Business  hours   Financial  closing   Holiday  shopping   Unpredictable  online  retailing   •  Non-­‐Produc3on  –  Short  term  instances   –  Conversion,  Training,  EAI,  Produc3on  clones   •  Long  procurement  cycles  to  add  capacity     •  No  ability  to  scale  down   Developed by
  14. 14. Developed by
  15. 15. •  Customers network can be connected to a VPC in Amazon •  IPSec/VPN or Hardware/VPN or Direct Connect •  All instances will only be accessible from customers network only and part of customers domain unless customer chooses otherwise. •  Instance will be strategically placed for very high availability •  Standby images will be created for Disaster recovery in a Alternate Zone/Region •  A Elastic Load balancer, Elastic IP and Route 53 will be used to make failure over transparent to end users Developed by
  16. 16. Developed by
  17. 17. •  •  •  •  •  In a region closest to customer site (e.g Virginia) two web servers to be placed Each Web server to be placed in separate AZ Additional stand by images will be kept in secondary region (e.g Oregon) Web servers can be load balanced using customers in house load balance or Amazon Elastic Load Balancer For DR failover times can be reduced by keeping stand by instances online Developed by
  18. 18. Scenario Solution Impact Web Server Fails Start a new instance from Stand by image within same AZ Slow Performance while stand by instances are added AZ failure ELB Managed. Launch Additional Instances on available AZ Slow Performance while stand by instances are added Region Failure DNS Failover. Startup web servers on the secondary region. Switch Route 53 entry for Web Server to point to ELB in Secondary Region. System will be unavailable while instances in stand by region come online • Impact can reduced if instances in secondary region are kept online High Load/Low Load Based on concurrent users, CPU and Memory additional standby instances can be turned on or existing Improved performance and TCO as infrastructure scales to according to demand Developed by
  19. 19. Developed by
  20. 20. •  •  •  •  •  In a region closest to customer site (e.g Virginia) three app servers will be deployed Each app server to be placed in separate AZ Additional stand by images will be kept in secondary region (e.g Oregon) Based on load additional stand by web servers can be brought online Siebel native load balancing to be used Developed by
  21. 21. Scenario Solution Impact App Server Fails Start standby app servers in the same AZ Reduced performance till instance is replaced AZ Failure Startup additional instance in online AZs Reduced performance till instance is replaced Region Failure Startup app servers on the secondary region. System will be unavailable while instances in stand by region come online * Impact can reduced if instances in secondary region are kept online High Load/Low Load Based on concurrent users, CPU and Memory additional standby app servers can be turned on or existing app servers can be turned off Improved performance and TCO as infrastructure scales to according to demand Developed by
  22. 22. Developed by
  23. 23. •  In a region closest to customer site (e.g Virginia) Gateway will be deployed •  siebns.dat will be backed up on S3 •  A stand by image will be kept in AZ in the same region •  Another stand by by image will kept in the same AZ •  A Elastic IP address pointing to active gateway instance •  A Route 53 entry for the gateway that points to the Elastic IP Developed by
  24. 24. Scenario Solution Impact Gateway Server Machine fails Copy the siebns.dat from S3 bucket to secondary Gateway. Start standby in secondary AZ. User sessions continue to run as is. Siebel Servers can not be started/shutdown and Siebel Admin disabled until secondary AZ gateway is online. AZ Failure Copy the siebns.dat from S3 bucket to secondary Gateway. Start standby in secondary AZ. User sessions continue to run as is. Siebel Servers can not be started/shutdown and Siebel Admin disabled until secondary AZ gateway is online. Region Failure Copy the siebns.dat from S3 bucket to standby instance in different region. Update Route 53 to point to secondary region gateway User sessions continue to run as is. Siebel Servers can not be started/shutdown and Siebel Admin disabled until secondary gateway form another region is online. Developed by
  25. 25. Developed by
  26. 26. Ac3ve   Applica3on   Server   Applica3on   Server   Applica3on   Server   Database   Server   Database   Server   Database   Server   Rapid  Clone   EBS  Middle   Tier   OLTP   Database   Server   OSB  Cloud   Module   Test  /  Dev   Produc3on  EBS   Corporate  Datacenter   Developed by Training   RMAN  Restore   Amazon S3 Bucket Region Project/POC  
  27. 27. Ac3ve   Not  Ac3ve  for   Produc3on  Traffic   Rsync  Replica3on   EBS  Middle   Tier   Applica3on   Server   Applica3on   Applica3on   Volume   Volume   Standby   Database   Database   Server   Server   OLTP   Database   Server   Produc3on  EBS   Corporate  Datacenter   Developed by Physical  Standby  /  Data  Guard   Data  Volume   Scaled Down Scaled Up Standby Production Servers Region OSB  Cloud   Module   Amazon S3 Bucket
  28. 28. Not  Ac3ve  for   Produc3on  Traffic   Ac3ve   Rsync  Replica3on   Applica3on   Server   Rapid  Clone   Applica3on   Server   EBS  Middle   Tier   Standby   Database   Server   OLTP   Database   Server   Produc3on  EBS   Corporate  Datacenter   Developed by Standby   Database   Server   Physical  Standby   RMAN   Restore   Data  Volume   Region Test/Dev  
  29. 29. •  •  •  •  •  Global manufacturing company with operations in APAC, Europe & North America (200 employees in North America) Complete Datacenter Migration to AWS Platform for North American Operations Microsoft SQL Server, IIS Application server and other infrastructure components Oracle E-Business Suite, Oracle BI, and various Business applications Services  provided  by  Apps  Associates   –  –  –  –  –  Cloud  Assessment  &  Enablement   Architecture  Design  and  Deployment   POC  &  Produc3on  Migra3on   Project  Management     24x7  Managed  Services  for  Produc3on  Opera3ons Developed by
  30. 30. Internet EBS OBIEE Lacrosse Windows Headquarters   VPC  Private  Subnet   Monitoring Solution Domain Controller Ping Identity MWA VPC  Public  Subnet   AZ-­‐1   Developed by US  East   Customer   Loca3on  2  
  31. 31. •  Global  manufacturing  company  with  opera3ons  in  7  countries   •  Oracle  BI  Analy3cs   –  Prod,  test,  dev  environments   •  Oracle  E-­‐Business  Suite   –  Implementa3on  phase   –  CRP  and  dev  environments   •  Apps  Associates  Services   •  Architecture  design,  deployment  and  24x7  managed  services  from  Apps  Associates  for   produc3on  opera3ons   Developed by
  32. 32. Internet EBS R12 OBIEE Headquarters   VPC  Private  Subnet   Monitoring Solution OpenVPN Interface for Remote Admin Team VPC  Public  Subnet   AZ-­‐1   Developed by US  East   Customer   Loca3on  2  
  33. 33. •  •  •  •  European  company  with  customer  base  worldwide,  providing  tax   solu3ons  integrated  to  ERP  environments   Oracle  E-­‐Business  Suite,  SAP   Instructor  led  mul3-­‐day  training  environments  for  custom  tax  solu3on   Apps  Associates  Services   •  Build  &  update  Gold  image   •  Spawn  Training  instances  on  Demand  in  minutes   •  Support  services  for  Training  instances   Developed by
  34. 34. Internet EBS R12 – App EBS R12 DB Trainer VPC Subnet SAP – App SAP DB VPC Subnet Students Developed by US East
  35. 35. Migration Challenges Challenges of Migrating to the AWS Cloud •  Migration of Large Databases (Timing) •  Customizations •  Connection to On-Premise Resources (i.e. LDAP, File Servers) •  Availability of Testing Team
  36. 36. •  The on-premise Oracle Enterprise Manager (EM12c) acts as a single tool to get a comprehensive view of your public AWS resources as well as your private cloud resources. •  Monitor EBS, EC2 and RDS instances on Amazon Web Services: •  Gather performance metrics and configuration details for AWS instances •  Raise alerts and violations based on thresholds set on monitoring •  Generate reports based on the gathered data •  Leverage the Enterprise Manager features such as system promotion, incident generation based on thresholds, integration with 3rd party ticketing applications etc. •  AWS Monitoring via this Plug-in is enabled via Amazon CloudWatch API and the users of this Plug-in are responsible for supplying credentials for accessing AWS and the CloudWatch API.
  37. 37. VPC OMS  /   EM  12c   OMR VPN Gateway Custom Scripts Staging Area VPN Tunnel Elastic Load Balancer EM AMI’s OMS  /   EM  12c   OMR OMR Private Subnet Amazon SES NAT   Common Repository – S3 Private Subnet VPC-­‐VPC   Tunnel   Instance   NAT   VPC-­‐VPC   Tunnel   Instance   Public Subnet Public Subnet Availability Zone Availability Zone Region OMS Backups Database Backups
  38. 38. Content Authors AWS US East Datapipe Virginia (Primary) Gateway S3 Logs S3 Media Public subnet Internet AWS IGW Oracle RAC Direct Connect NAT SG1 Amazon Route 53 us-east-1D us-east-1C us-east-1B Private subnet (2 Gbps) Autoscale Group Autoscale Group VPN Gateway SG2 Internet DB Replication (1 Gbps) Direct Connect ELB 1 (2 Gbps) ELB 2 Web Tier Instances Datapipe Somerset (Failover) App Tier Instances (Apache+WLS Plug-in) (WLS) SG3 Student / Instructor ELB 3 Gateway Mgmt subnet IPSec VPN Checkpoint VPN Gateway Monitor DNS NTP MySql Snorby rsyslog IPSec VPN IPSec VPN MHE DataCenter Wipro CCC MHE DMZ Gateway Student / Instructor LLB GLB EzTo Admin VPC Admin Console Connect Classware LSI Oracle RAC
  39. 39. Capgemini uses AWS to host the development, test and production Oracle E-Business Suite Financials supporting their business in Latin America. KPIT Cummins runs their Oracle E-Business Suite 12.1.3 environments on Amazon EC2/OVM. They have benefitted from the reduced complexity of AWS “infrastructure at a click.” Advanced Innovations hosts their entire Oracle Applications and technology platform on Amazon EC2. SOA Suite, WebCentre, Beehive, Ebusiness etc. Blue Gecko deployed SAGE Manufacturing’s dev, test, DR and production Oracle E-Business Suite environments on Amazon EC2.
  40. 40. Oracle eBusiness Suite 11 - Imperia was established officially on February 3rd, 1932 as the development of a little artisan workshop and started at once to distribute pasta machines around the world. McGraw-Hill migrated an Oracle WebLogic and Oracle RAC environment to AWS using a hybrid architecture. Oracle WebLogic is clustered on EC2 using ELB and Auto Scaling. The Oracle RAC Database runs in Data Pipe.
  41. 41. Four Node Exadata Primary Site" Client" Standby on Amazon Web Services" Client" Client" Client" REDO APPLY" Amazon" EC2" BROKER AGENT" Oracle E-Business Suite 11i on Oracle Exadata Amazon Elastic Block Storage (EBS) EC2! BROKER
 AGENT! Data Guard Broker! RDBMS 11gR2" Primary LIFE Database Amazon" S3" Standby LIFE 1DG Database
  42. 42. Test Drive Labs New AMIs Bigger Oracle OpenWorld Presence 2013 Updated FAQ and Licensing Document Customer Successes Reference Implementations Re:Invent Sessions White Papers
  43. 43. Here are some additional resources: •  Oracle Test Drives : •  Running Oracle on AWS: •  Oracle FAQ: •  Oracle Secure Backup Cloud Module product Page: •  Oracle AWS cloud licensing document: •  Oracle Enterprise Manager 12c plug in: •  Recorded sessions: –  smartShift customer success : –  Oracle on AWS : 729/667/988620541967729667/2-988620541967729667-13e6bb61c33.asx –  Oracle OEM12c Hosted on AWS :
  44. 44. •  Attend AWS re:Invent Oracle Related Sessions –  –  –  –  –  –  DAT202 - Using Amazon RDS to Power Enterprise Applications DAT401 - Advanced Data Migration Techniques for Amazon RDS STG301 - AWS Storage Tiers for Enterprise Workloads - Best Practices STG305 - Disaster Recovery Site on AWS - Minimal Cost Maximum Efficiency STG303 - Running Microsoft and Oracle Stacks on Elastic Block Store ENT303 - Migrating Enterprise Applications to AWS - Best Practices, Tools and Techniques Register here: trk=PS_reinvent2013_Brand_AWS_Sessions_BMM