2 Contributors The following individuals and organizations contributed to this document Ashok Sundaram, Solutions Architect, Amazon Web Services Milind Waikul, CEO, Enterprise Beacon, Inc. Mark Farrier, Director Product Management Siebel CRM, Oracle
3 Contents Contributors... 2 Overview... 5 Benefits of running Siebel on AWS... 5 Key Benefits over On Premise... 5 Key Benefits over SAAS... 7 Amazon Web Services Concepts... 8 Regions... 8 Availability Zones... 8 Elastic Compute Cloud (EC2)... 9 Relation Database Service (RDS)... 9 Elastic Load Balancer (ELB)... 9 Elastic Block Store Amazon Machine Image Simple Storage Service Route Virtual Private Cloud Direct Connect Siebel and Oracle Licensing on AWS Siebel and Oracle database license portability Amazon RDS for Oracle licensing models Oracle database BYOL licensing on AWS Best practices for deploying on AWS Use multiple Availability Zones for HA Siebel user traffic distribution and load balancing Stand by instances Siebel Gateway server high availability Database high availability VPC deployment and connectivity options The AWS Security Model AWS Identity and Access Management (IAM) Monitoring and Logging Network Security and Virtual Private Cloud (VPC)... 16
4 Migration scenarios and best practices Monitoring your infrastructure Disaster Recovery Production and DR on AWS - Cross region deployment DR on AWS Production on premise Conclusion AWS and Oracle Support AWS Support Oracle Support References... 21
5 Overview Companies are increasingly adopting the Cloud First and Mobile First strategy. Moving Siebel to the cloud is not only an option that needs to be considered, but this option is likely becoming a necessity. This paper is intended to help customers understand Amazon Web Services (AWS) and how to leverage AWS for Oracle Siebel CRM along with best practices for customers. The key benefits are: Lower Total Cost of Ownership (TCO) - Reduced overall expenditure for computing resources Elasticity to grow environments on an as needed basis Agility spin up environments in minutes rather than days Leverage faster and cheaper computing technology as it becomes available High Availability Low cost disaster recovery Benefits of running Siebel on AWS Migrating Siebel to AWS is relatively simple and straight forward. However it is important not to view this as a physical to virtual conversion. Understanding the AWS components and capabilities will help customers make the most of their Siebel on AWS. Key Benefits over On Premise Eliminate long procurement cycles: The Traditional Deployment as shown in the image below is a long process with each stage being time intensive and requiring large capital outlay and multiple approvals.
6 This process has to be repeated for the various environments e.g. development, testing, training, break fix and production which compounds the costs and causes significant delays. Have Moore s law working for you instead of against you: Customers end up owning hardware that is depreciating in value every year. Customers cannot simply add more computing capacity as it is needed. Customers are locked into the price and capacity of the hardware once it is acquired in addition to the ongoing hardware support costs. With AWS, customers can switch their underlying Siebel instances to newer AWS instances types with just once click. Right Size Anytime: Often customer end up over sizing environments for initial phases and then are unable to cope with growth in later phases. With AWS customers can scale the usage up or down at any time and only pay for the computing capacity the use and for the duration it is used. Instance sizes can be changed in minutes via the AWS Management Console or the AWS Application Programming Interface (API) or Command Line Interface (CLI). Resilience and ability to keep recovering from multiple failures: Siebel On Premise failures have to be handled on a case by case basis. Failed parts have to procured and replaced. Key components like the Siebel gateway have to be clustered using expensive clustering software and deployment is still limited by its ability to handle only one failure in the primary gateway. With AWS clustering of the Siebel gateway is not required and the gateway can recover from multiple failures using the AWS EC2 auto recovery feature. Disaster Recovery: Customers can build extremely low cost stand by DR environments for their existing deployments and incur costs only for the duration of the outage. Incidental costs: On Premise customers typically pay hardware support costs, virtualization licensing and support, data center costs etc. All these can be eliminated or reduced by moving to AWS. Ability to test application performance: As a rule, even though performance testing is recommended prior to any major change to a Siebel environment, most customers only performance test their Siebel application during the initial launch in the yet to be deployed production hardware. Siebel customers usually never performance test later releases due to the expense and lack of the environment required for performance testing. This added risk of discovering performance issues later in production can be easily eliminated with the use of AWS. An environment can be created easily and quickly just for the performance testing duration and only used when needed. Again customer is charged only for the hours the environment is used. No End of Life (EOL) for Hardware/Platform: All Hardware Platforms have EOL dates, at which point the hardware is no longer supported, customer are forced to buy new hardware again. In the AWS cloud, customers can simply upgrade the platform instances to new AWS instance types in a single click at no cost for the upgrade. High Availability: Designed correctly a minimum of 99.95% uptime can be achieved on AWS cloud at no additional cost. This far exceeds the Service Level Agreement (SLA) of
7 most customer s data centers it is possible to achieve SLA s greater than 99.95% at some additional cost and correct infrastructure design. No need for clustering: The Siebel Gateway is a single point of failure. On premise implementations require the gateway to be clustered. Clustering is complicated and expensive to implement. With AWS no clustering is needed and a failed Gateway can be automatically recovered using the AWS EC2 auto recovery feature. Unlimited Environments: On Premise customer always face limited environments as an issue. e.g. test environments will have a newer release compared to production, if a performance issue is found in production the customer has no way of suddenly provisioning a performance debugging environment. On AWS this can be done very easily. Key Benefits over SAAS Lower Total Cost of Ownership (TCO): Existing Siebel customers do not have to purchase new CRM licenses or risk a re-implementation of their CRM, they can just move their existing Siebel implementation to AWS. For new customers the TCO is still low as they do not have to pay endless monthly SAAS license fees and Siebel is proven CRM with rich verticals. Security: SAAS solutions require public access. On AWS, Siebel can be deployed in a Virtual Private Cloud (VPC) and the VPC can be connected to the customers on premise data center using AWS Direct Connect, bypassing the public internet. Using AWS Direct Connect customers can extend their on premise data centers to the cloud and the Siebel instances can be assigned private IP s that are part of customer s internal network. SAAS has to be accessed over public internet making it less secure and requires a lot of effort for integrating existing backend systems and identity management. Unlimited usage: SAAS applications have governor/platform limits to accommodate underlying multi-tenant architecture. Governor limits restrict everything from number of API calls, transaction times to data sets, and file sizes. With AWS cloud Siebel customers can self-provision and use as much or as little capacity as needed and have to pay only for what they use. Multi-tenant vs Elastic: SAAS products typically use a multi tenanted architecture which ties the customers to a specific instance and limits of that instance. With AWS customers have complete control over the computing capacity they provision and customers can provision as much or as little as needed. Single application: With Siebel customer can manage everything from Marketing, Sales, Service, CPQ and Order Management in one application. On SAAS this requires multiple applications that customer have to buy and integrate. The cost of integration with SAAS applications is easy to overlook in the buy decision but these costs can add up significantly later.
8 Amazon Web Services Concepts Regions Amazon Web Services (AWS) serves over a million active customers in more than 190 countries and AWS services are available from 11 regions worldwide. Each region is a separate geographic area isolated from the other regions. Regions provide you the ability to place resources, such as EC2 instances, and data in multiple locations. Resources aren't replicated across regions unless you do so specifically. AWS provides multiple regions so that you can launch your application in locations that meet your requirements. For example, you might want to launch in Europe to be closer to your European customers or to meet legal requirements. Availability Zones Each region has multiple, isolated locations known as Availability Zones. Each availability zone runs on its own physically distinct, independent infrastructure, and is engineered to be highly reliable. Common points of failures like generators and cooling equipment are not shared across Availability Zones. Additionally, they are physically separate, such that even extremely uncommon disasters such as fires, tornados or flooding would only affect a single Availability Zone. Each Availability Zone is isolated, but the Availability Zones in a region are connected through low-latency links. The following diagram illustrates the relationship between regions and Availability Zones.
9 Elastic Compute Cloud (EC2) Amazon Elastic Compute Cloud (EC2) is a web service that provides resizable compute capacity in the cloud that is billed by the hour. You can run virtual machines ranging in size from 1 ECU and 1 GB memory to 36 ECU and 244 GB memory. You have a choice of operating systems including Windows Server 2008/2012, Oracle Linux, Red Hat Enterprise Linux and SUSE Linux. Relation Database Service (RDS) Amazon Relation Database Service (RDS) makes it easy to set up, operate, and scale a relational database in the cloud. It provides cost-efficient and resizable capacity while managing time-consuming database administration tasks, freeing customers up to focus on their applications and business. For Siebel, both MSSQL and Oracle databases are available. Elastic Load Balancer (ELB) Amazon Elastic Load Balancing (ELB) automatically distributes incoming application traffic across multiple Amazon EC2 instances in the cloud. It enables you to achieve greater levels of fault tolerance in your applications, seamlessly providing the required amount of load balancing capacity needed to distribute application traffic. ELB can be used for load balancing Siebel web server traffic.
10 Elastic Block Store Amazon Elastic Block Store (EBS) provides persistent block level storage volumes for use with Amazon EC2 instances in the AWS Cloud. Each Amazon EBS volume is automatically replicated within its Availability Zone to protect you from component failure, offering high availability and durability. Amazon EBS volumes offer the consistent and low-latency performance needed to run your workloads. Amazon Machine Image An Amazon Machine Image (AMI) is simply a packaged-up environment that includes all the necessary bits to set up and boot your instance. Your AMIs are your unit of deployment. Amazon EC2 uses Amazon EBS and Amazon S3 to provide reliable, scalable storage of your AMIs so that we can boot them when you ask us to do so. Simple Storage Service Amazon Simple Storage Service (S3) provides developers and IT teams with secure, durable, highly-scalable object storage. Amazon S3 is easy to use, with a simple web services interface to store and retrieve any amount of data from anywhere on the web. With Amazon S3, you pay only for the storage you actually use. There is no minimum fee and no setup cost. Route 53 Amazon Route 53 is a highly available and scalable cloud Domain Name System (DNS) web service. It is designed to give developers and businesses an extremely reliable and cost effective way to route end users to Internet applications by translating names like into the numeric IP. Virtual Private Cloud Amazon Virtual Private Cloud (Amazon VPC) lets customers provision a logically isolated section of the Amazon Web Services (AWS) Cloud where customers can launch AWS resources in a virtual network that customers define. Customers have complete control over their virtual networking environment, including selection of their own private IP address range, creation of subnets, and configuration of route tables and network gateways. You can leverage multiple layers of security, including security groups and network access control lists, to help control access to Amazon EC2 instances in each subnet. Additionally, you can create a Hardware Virtual Private Network (VPN) connection between your corporate
11 Direct Connect datacenter and your VPC and leverage the AWS cloud as an extension of your corporate datacenter. AWS Direct Connect is a network service that provides an alternative to using the Internet to utilize AWS cloud services. Using AWS Direct Connect, you can establish private dedicated network connectivity between AWS and your datacenter, office, or colocation environment, which in many cases can reduce your network costs, increase bandwidth throughput, and provide a more consistent network experience than Internet-based connections. Siebel and Oracle Licensing on AWS Siebel and Oracle database license portability Most Oracle Software licenses are fully portable to Amazon Web Services (AWS), including Enterprise License Agreement (ELA), Unlimited License Agreement (ULA), Business Process Outsourcing (BPO) and Oracle Partner Network (OPN). Most Siebel customers can use their existing Siebel license and Oracle database licenses on AWS just like they would use them On Premise; however customer should consult their own Oracle license agreement for specific information. Amazon RDS for Oracle licensing models You can run Amazon RDS for Oracle under two different licensing models License Included and Bring-Your-Own-License (BYOL). In the "License Included" service model (available only for Oracle Standard Edition One), you do not need to separately purchase Oracle licenses; the Oracle Database software has been licensed by AWS. "License Included" pricing starts at $0.04 per hour, inclusive of software, underlying hardware resources, and Amazon RDS management capabilities. If you already own Oracle Database licenses, you can use the "BYOL" model to run Oracle databases on Amazon RDS, with rates starting at $0.025 per hour. The BYOL model is designed for customers who prefer to use existing Oracle database licenses or purchase new licenses directly from Oracle. Oracle database BYOL licensing on AWS Oracle licensing on AWS is based on Oracle s cloud licensing policy available here: Processor Based Licensing For the purposes of licensing Oracle programs in an Authorized Cloud Environment like AWS EC2 and RDS, customers are required to count each virtual core on the instance as equivalent to a physical core. The vcpu count on the instance is not relevant to licensing Oracle databases on AWS, you have to use the virtual core count while licensing Oracle
12 databases on AWS. The number of virtual cores on each AWS EC2 and RDS instance type can be found here: Edition Limitations When licensing Oracle programs with Standard Edition One or Standard Edition in the product name (e.g. Oracle Database Standard Edition One or Oracle Database Standard Edition), the pricing is based on the size of the instance. EC2 instances with 4 or fewer virtual cores are counted as 1 socket, which is considered equivalent to a processor license. For EC2 instances with more than 4 virtual cores, every 4 virtual cores used (rounded up to the closest multiple of 4) equate to a licensing requirement of 1 socket. Under this cloud computing policy, Oracle Database Standard Edition may only be licensed on EC2 and RDS instances with up to 16 virtual cores and Oracle Database Standard Edition One may only be licensed on EC2 and RDS instances with up to 8 virtual cores. Oracle Database Enterprise Edition has no virtual core limitations. Licensing Examples Example, for Database Enterprise Edition licensing on AWS EC2: Licensing Oracle Database Enterprise Edition on a single EC2 r3.4xlarge instance or RDS db.r3.4xlarge with 8 virtual cores would require 8 * 0.5 = 4 processor licenses (0.5 is the core multiplication factor for Intel multicore chips; from the Oracle Processor Core Factor Table here pdf and each virtual core is considered equivalent to a physical core) Example, for Database Standard Edition licensing on AWS EC2: For an EC2 instance containing 1 to 4 virtual cores (like the EC2 r3.xlarge or RDS db.r3.xlarge with 2 virtual cores and the EC2 r3.2xlarge or RDS db.r3.2xlarge with 4 virtual cores), the number of Oracle Database Standard Edition licenses required will be 1 processor license. On an EC2 instance with 5 to 8 virtual cores (like EC2 r3.4xlarge or RDS db.r3.4xlarge with 8 virtual cores), two processor licenses would be needed. These examples noted above are for illustrative purposes only and based on Oracle s cloud licensing policy as on Sep 16th 2015; you should consult your own Oracle license agreement for specific information.
13 Best practices for deploying on AWS Use multiple Availability Zones for HA Each Availability Zone (AZ) is isolated from other AZs and runs on its own physically distinct, independent infrastructure. The likely hood of two AZs experiencing a failure at the same time is relatively small and you can spread your Siebel web server and app server instances across multiple AZs to ensure high availability of your application. Deploy the Siebel database on Amazon RDS in multi-az configuration. Amazon RDS Multi-AZ deployments provide enhanced availability and durability for Database (DB) Instances, making them a natural fit for production database workloads. When you provision a Multi-AZ DB Instance, Amazon RDS automatically creates a primary DB Instance and synchronously replicates the data to a standby instance in a different Availability Zone (AZ).
14 Siebel user traffic distribution and load balancing Use Route 53 DNS to direct users to Siebel hosted on AWS. Use Elastic Load Balancing to distribute incoming traffic across the Siebel web servers deployed in multiple Availability Zones. The load balancer serves as a single point of contact for clients, this enables you to increase the availability of your application. You can add and remove Siebel web server instances from your load balancer as your needs change, without disrupting the overall flow of information. Elastic Load Balancing ensures that only healthy Siebel Web Server instances receive traffic by detecting unhealthy instances and rerouting traffic across the remaining healthy instances. If a Siebel web server instance fails, Elastic Load Balancing automatically reroutes the traffic to the remaining running Siebel web server instances. If a failed Siebel web server instance is restored, Elastic Load Balancing restores the traffic to that instance. Stand by instances To meet extra capacity requirements additional instances of Siebel Web Server and App Servers can be installed and configured on EC2 instances, these stand by instances can be shutdown till the time the extra capacity is required. EC2 charges are not incurred when instances are shutdown only EBS storage charges are incurred. As of writing this paper EBS charges are $0.05 per GB per month e.g. for an instance with 120 GB HDD space the storage charge is only $6 per month. These pre-installed stand by instances provides the flexibility for a customer to use these instances for meeting additional capacity needs as and when required. Siebel Gateway server high availability With bare metal implementations customers are used to deploying Siebel Gateway in an active passive cluster to ensure availability of the Siebel Gateway in case of host failure. When deploying on AWS there are several options for configuring Siebel gateway server high availability. You can use the EC2 auto-recovery feature to recover the Siebel Gateway in case of failure of the underlying host. When using EC2 auto-recovery a number of system status checks monitor the instance and the other components that need to be running in order for your instance to function as expected. Among other things, the checks look for loss of network connectivity, loss of system power, software issues on the physical host, and hardware issues on the physical host. If a system status check of the underlying hardware fails, the instance will be rebooted (on new hardware if necessary) but will retain its Instance Id, IP Address, Elastic IP Addresses, EBS Volume attachments, and other configuration details. Another option is to put the Siebel gateway servers in an auto scaling group spanning multiple availability zones and set the min and max size of the group to one. Auto scaling will ensure that an instance of the Siebel gateway server is running in any of the selected availability zones. This solution ensures Siebel gateway server high availability in the unlikely event of an Availability Zone failure. When using both the above options you should backup siebns.dat to Amazon S3 prior to and after making any configuration changes, especially creating new component definitions and adding or deleting Siebel Servers. When the Siebel Gateway server is restored after a failure,
15 it should bootstrap and update itself with the latest copy of siebns.dat from S3. You don t have to buy additional software or run additional passive instances while using auto recovery or a fixed size auto scaling group for high availability. Alternatively you can also configure high availability by clustering the Siebel gateway server. There are several third party products like SIOS and SoftNas available that offer a shared storage solution on AWS for clustering the Siebel gateway server. Database high availability Deploy the Siebel database on Amazon RDS in multi-az configuration. Amazon RDS Multi-AZ deployments provide enhanced availability and durability for Database (DB) Instances, making them a natural fit for production database workloads. When you provision a Multi- AZ DB Instance, Amazon RDS automatically creates a primary DB Instance and synchronously replicates the data to a standby instance in a different Availability Zone (AZ). Each AZ runs on its own physically distinct, independent infrastructure, and is engineered to be highly reliable. In case of an infrastructure failure (for example, instance hardware failure, storage failure, or network disruption), Amazon RDS performs an automatic failover to the standby, so that you can resume database operations as soon as the failover is complete. Since the endpoint for your DB Instance remains the same after a failover, your application can resume database operation without the need for manual administrative intervention. VPC deployment and connectivity options Amazon Virtual Private Cloud (Amazon VPC) lets customers provision a secure, private, isolated section of the AWS cloud where they can launch AWS resources in a virtual network using customer-defined IP address ranges. Amazon VPC provides customers with several options for connecting their AWS virtual networks with other remote networks securely. If the users are primarily accessing the Siebel application from office or on premise (e.g. a call center scenario), you can use a hardware IPSEC VPN connection or AWS Direct Connect to connect your on premise network and AWS VPC. If the users are accessing the Siebel application from outside the office (e.g. a sales rep or customer accessing Siebel from the field or from home) you can use a Software appliance-based VPN connection over the Internet. Please refer to the below whitepaper for detailed information on various connectivity options. The AWS Security Model The AWS infrastructure has been architected to provide an extremely scalable, highly reliable platform that enables customers to deploy applications and data quickly and securely. Security in the cloud is slightly different than security in your on-premises data centers. When you move computer systems and data to the cloud, security responsibilities become shared between you and your cloud service provider. In this case, AWS is responsible for securing the underlying infrastructure that supports the cloud, and you are responsible for securing workloads you deploy in AWS. This shared security responsibility model can reduce your
16 operational burden in many ways, and gives you the flexibility you need to implement the most applicable security controls for your business functions in the AWS environment. It s recommended to take advantage of the various security features AWS offers when deploying Siebel on to AWS. Some of them are listed below AWS Identity and Access Management (IAM) With IAM, you can centrally manage users, security credentials such as passwords, access keys, and permissions policies that control which AWS services and resources users can access. IAM supports multifactor authentication for privileged accounts, including options for hardwarebased authenticators and support for Integration, and federation, with corporate directories to reduce administrative overhead and improve end-user experience. Monitoring and Logging AWS CloudTrail is a web service that records AWS API calls for your account and delivers log files to you. The recorded information includes the identity of the API caller, the time of the API call, the source IP address of the API caller, the request parameters, and the response elements returned by the AWS service. This provides deep visibility into API calls, including who, what, when, and from where calls were made and the AWS API call history produced by CloudTrail enables security analysis, resource change tracking, and compliance auditing. Network Security and Virtual Private Cloud (VPC) Amazon Virtual Private Cloud (VPC) lets you provision a logically isolated section of the AWS Cloud where you can launch AWS resources in a virtual network that you define and provides the ability to use an IPsec Virtual Private Network (VPN) device to provide an encrypted tunnel between the Amazon VPC and your data center. You create one or more subnets within each Amazon VPC; each instance launched in the Amazon VPC is connected to one subnet. Traditional Layer 2 security attacks, including MAC spoofing and ARP spoofing, are blocked. You can configure network ACLs, these are stateless traffic filters that apply to all traffic inbound or outbound from a subnet within Amazon VPC.
17 These ACLs can contain ordered rules to allow or deny traffic based upon IP protocol, by service port, as well as source/destination IP address. Security Groups are a complete firewall solution enabling filtering on both ingress and egress traffic from an instance. Traffic can be restricted by any IP protocol, by service port, as well as source/destination IP address (individual IP or Classless Inter-Domain Routing (CIDR) block). Data Encryption AWS offers you the ability to add a layer of security to your data at rest in the cloud, providing scalable and efficient encryption features. Data encryption capabilities are available in AWS storage and database services, such as EBS, S3, Glacier, Oracle RDS, SQL Server RDS, and Redshift. Flexible key management options allow you to choose whether to have AWS manage the encryption keys (via the AWS Key Management Service (KMS)) or maintain complete control over your keys. Dedicated, hardware-based cryptographic key storage options (AWS CloudHSM) are available for customers to help satisfy compliance requirements. Please refer to the following AWS white papers for more info: and Migration scenarios and best practices Each customer could potentially have a different migration scenario. This section covers some of the most common scenarios. Migrate existing Siebel environments to AWS This is most suitable for customers that are on a recent release of Siebel. Customers should design their AWS deployments based on the best practices in this white paper. Siebel Upgrade Customers can leverage AWS as the upgrade environment in order to keep costs of upgrade to a minimum. In the end customers have option to leverage this new environment for test and development only or they can choose to migrate their entire Siebel environment to AWS. Either way it s a win for the customer and Siebel as the overall TCO can be reduced. Performance testing Most customers only do performance testing for Siebel changes either on initial implementation or only when they have Siebel upgrades to put in place. There is almost never any testing for customer enhancements that continually are done with the configuration product tools. Using AWS enables a new way to accomplish this with minimal cost as the resources to do this are only charged for when they are actually used with performance test runs. This minimal cost will enable more realistic testing both for Siebel
18 upgrades and for customer enhancements and can be budgeted for on an annual basis depending upon normal customer need cycles for when SRF changes are put in place. This will allow customers to both reduce performance issues and also even avoid business critical downtimes with this availability of more real world testing of their own planned changes/enhancements. Siebel Test and Development environments on AWS Customers may choose to just setup Test and Developments on AWS for testing out AWS or just setting up additional Test and Developments environment needs if the move of the production environment is not urgent. Disaster Recovery (DR) on AWS Customer may want to setup a DR environment for their existing Siebel CRM on AWS which can be done at a much lower cost than setting up traditional DR. Monitoring your infrastructure For monitoring their Siebel application customers can continue to use the existing tools that they are familiar with. Customers can also use Amazon CloudWatch to monitor AWS cloud resources and the applications they run on AWS. Amazon CloudWatch enables you to monitor your AWS resources in near real-time, including Amazon EC2 instances, Amazon EBS volumes, Elastic Load Balancers, and Amazon RDS DB instances. Metrics such as CPU utilization, latency, and request counts are provided automatically for these AWS resources. You can also supply your own logs or custom application and system metrics, such as memory usage, transaction volumes, or error rates, and Amazon CloudWatch will monitor these too. Customers can use Amazon CloudWatch to gain system-wide visibility into resource utilization, application performance, and operational health. Customers can use these insights to monitor and keep their applications running smoothly. Disaster Recovery This section provides an overview and some example scenarios for leveraging AWS for Siebel Disaster Recovery (DR). Cross region deployments for DR should be designed and validated for specific use cases based on customer uptime needs and budget.
19 Production and DR on AWS - Cross region deployment Customer can consider cross region deployments if they want to implement a disaster recovery solution for their Siebel application. The above diagram depicts a typical Siebel deployment across regions that addresses both high availability and DR requirements. The users are directed to the Siebel application in the primary region using Amazon Route53. In case the primary region is unavailable due to a disaster, fail over is initiated and the users will be redirected towards the Siebel application deployed in the DR region. The database is deployed on Oracle running on EC2 instances and Oracle Data Guard replication is configured between the primary database and two standby databases; one local standby database (synchronous replication) in another availability zone in the primary region and another remote standby database (asynchronous replication) in the DR region. In case of failure of the primary database, the local standby database is promoted as the primary and the Siebel application will connect to it. In the extremely unlikely event of a region failure or unavailability, the remote standby is promoted as the primary and users are redirected to Siebel application in the DR region using Route53. Please refer to this AWS whitepaper for in depth coverage on using AWS for Disaster Recovery DR on AWS Production on premise Customers can use AWS to deploy DR environments for Siebel applications running on premise. In this scenario the production environment is on premise and the DR environment is deployed on AWS. If the production environment fails, a failover is initiated and users are redirected to
20 the Siebel application deployed on AWS. The process is fairly simple and involves the following major steps. Setup connectivity between on premise data center and AWS using VPN or AWS Direct Connect. Install Siebel web, application and Gateway servers on AWS. Back up siebns.dat to S3. Install the standby database on AWS and configure Oracle Data Guard replication between the on premise production database and the standby database on AWS. When the production environment on premise fails, initiate a failover and redirect users to the Siebel application on AWS. Conclusion By deploying Siebel on the AWS cloud customers can reduce costs and at the same time enable capabilities that might not be possible or cost effective if deployed in the customer s data center e.g. Low cost resources are billed by the hour and only for the duration they are used. Changing of Cap Ex to Op Ex eliminates need for large capital layout. Higher availability of 99.95% by deploying Siebel in a Multi-AZ configuration. Flexibility to add capacity elastically for coping with demand i.e. right size environment at any time. Flexibility to add environments and use them for short durations e.g. performance testing and training. AWS and Oracle Support AWS Support AWS Support is a one-on-one, fast-response support channel that is staffed around the clock with technical support engineers and experienced customer service professionals who help you get the most from the products and features provided by Amazon Web Services. All AWS Support tiers offer an unlimited number of support cases with pay-by-the-month pricing and no long-term contracts. The four tiers provide developers and businesses the flexibility to choose the support tiers that meet their specific needs. AWS Support Business and Enterprise levels include support for common operating systems and common application stack components. AWS Support engineers can assist with the setup, configuration and troubleshooting of the certain third-party platforms and applications including Red Hat Enterprise Linux, SUSE Linux, Windows server 2008 & 2012, Open VPN, RRAS etc. More details on AWS support can be found here:
21 Oracle Support Customers will be leveraging their existing licenses for Siebel Applications that they had with their On Premise implementations, they will already have same level of Oracle Support that they had with OP. Oracle s only requirement for IaaS clouds is that customer s use platforms and databases that are certified with Siebel and versions of both Siebel and Platform/database that are documented on the Oracle support site. Customer can submit issues in the same manner and provide information about their environments as before. The fact that IaaS cloud is in use may not even enter the discussion as there is nothing specific about these clouds being used that require any change to the application for their use. This is the same approach for virtual technology that Oracle support has followed with Siebel for many years now. Escalations would follow the same process customer s use now via the customer support site. It would be no different for customer using IaaS clouds References Test drive Siebel running EC2 and RDS EC2 documentation RDS documentation AWS Cloud Watch AWS Cost Estimator AWS Trusted Advisor Oracle cloud licensing Oracle Processor Core Factor Table AWS EC2 Virtual Cores by Instance Type : AWS VPC connectivity options AWS Security: AWS Security best practices Disaster Recovery on AWS AWS Support: SIOS - SoftNas -
Amazon EC2 Product Details Page 1 of 5 Amazon EC2 Functionality Amazon EC2 presents a true virtual computing environment, allowing you to use web service interfaces to launch instances with a variety of
Overview and Deployment Guide Sophos UTM on AWS Overview and Deployment Guide Document date: November 2014 1 Sophos UTM and AWS Contents 1 Amazon Web Services... 4 1.1 AMI (Amazon Machine Image)... 4 1.2
Application Security Best Practices Matt Tavis Principal Solutions Architect Application Security Best Practices is a Complex topic! Design scalable and fault tolerant applications See Architecting for
How AWS Pricing Works (Please consult http://aws.amazon.com/whitepapers/ for the latest version of this paper) Page 1 of 15 Table of Contents Table of Contents... 2 Abstract... 3 Introduction... 3 Fundamental
P3 InfoTech Solutions Pvt. Ltd http://www.p3infotech.in July 2013 Created by P3 InfoTech Solutions Pvt. Ltd., http://p3infotech.in 1 Web Application Deployment in the Cloud Using Amazon Web Services From
How AWS Pricing Works May 2015 (Please consult http://aws.amazon.com/whitepapers/ for the latest version of this paper) Page 1 of 15 Table of Contents Table of Contents... 2 Abstract... 3 Introduction...
Opsview in the Cloud Monitoring with Amazon Web Services Opsview Technical Overview Page 2 Opsview In The Cloud: Monitoring with Amazon Web Services Contents Opsview in The Cloud... 3 Considerations...
RemoteApp Publishing on AWS WWW.CORPINFO.COM Kevin Epstein & Stephen Garden Santa Monica, California November 2014 TABLE OF CONTENTS TABLE OF CONTENTS... 2 ABSTRACT... 3 INTRODUCTION... 3 WHAT WE LL COVER...
Cloud Models and Platforms Dr. Sanjay P. Ahuja, Ph.D. 2010-14 FIS Distinguished Professor of Computer Science School of Computing, UNF A Working Definition of Cloud Computing Cloud computing is a model
Active Directory Domain Services on the AWS Cloud: Quick Start Reference Deployment Mike Pfeiffer March 2014 Last updated: September 2015 (revisions) Table of Contents Abstract... 3 What We ll Cover...
Amazon Compute - EC2 and Related Services G-Cloud Service 1 1.An overview of the G-Cloud Service Arcus Global are approved to sell to the UK Public Sector as official Amazon Web Services resellers. Amazon
DLT Solutions and Amazon Web Services For a seamless, cost-effective migration to the cloud PREMIER CONSULTING PARTNER DLT Solutions 2411 Dulles Corner Park, Suite 800 Herndon, VA 20171 Duane Thorpe Phone:
Amazon Cloud Storage Options Table of Contents 1. Overview of AWS Storage Options 02 2. Why you should use the AWS Storage 02 3. How to get Data into the AWS.03 4. Types of AWS Storage Options.03 5. Object
DISTRIBUTED SYSTEMS [COMP9243] Lecture 9a: Cloud Computing Slide 1 Slide 3 A style of computing in which dynamically scalable and often virtualized resources are provided as a service over the Internet.
Amazon Relational Database Service User Guide Amazon Relational Database Service: User Guide Copyright 2014 Amazon Web Services, Inc. and/or its affiliates. All rights reserved. The following are trademarks
Software- as- a- Service (SaaS) on AWS Business and Architecture Overview SaaS and AWS Introduction Software- as- a Service (SaaS) is an application delivery model that enables users to utilize a software
Running Oracle on the Amazon Cloud Bryan Stroble RMOUG Training Days February 7, 2014 Oracle Experts, Easy to Work With Oracle experts Oracle Database Technology Consulting Oracle E-Business Suite Applications
Amazon Relational Database Service (RDS) G-Cloud Service 1 1.An overview of the G-Cloud Service Arcus Global are approved to sell to the UK Public Sector as official Amazon Web Services resellers. Amazon
The following text is partly taken from the Oracle book Middleware and Cloud Computing It is available from Amazon: http://www.amazon.com/dp/0980798000 Cloud Databases and Oracle When designing your cloud
Using ArcGIS for Server in the Amazon Cloud Randall Williams, Esri Subrat Bora, Esri Esri UC 2014 Technical Workshop Agenda What is ArcGIS for Server on Amazon Web Services Sounds good! How much does it
Preparing Your IT for the Holidays A quick start guide to take your e-commerce to the Cloud September 2011 Preparing your IT for the Holidays: Contents Introduction E-Commerce Landscape...2 Introduction
Managing Your Microsoft Windows Server Fleet with AWS Directory Service May 2015 2015, Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational
19.10.11 Amazon Elastic Beanstalk A Short History of AWS Amazon started as an ECommerce startup Original architecture was restructured to be more scalable and easier to maintain Competitive pressure for
Microsoft Windows Server Failover Clustering (WSFC) and SQL Server AlwaysOn Availability Groups on the AWS Cloud: Quick Start Reference Deployment Mike Pfeiffer July 2014 Last updated: September 2015 (revisions)
Implementing Microsoft Windows Server Failover Clustering (WSFC) and SQL Server 2012 AlwaysOn Availability Groups in the AWS Cloud David Pae, Ulf Schoo June 2013 (Please consult http://aws.amazon.com/windows/
FortiGate-AWS Deployment Guide FortiGate-AWS Deployment Guide September 25, 2014 01-500-252024-20140925 Copyright 2014 Fortinet, Inc. All rights reserved. Fortinet, FortiGate, FortiCare and FortiGuard,
Primex Wireless OneVue Architecture Statement Secure, cloud-based workflow, alert, and notification platform built on top of Amazon Web Services (AWS) 2015 Primex Wireless, Inc. The Primex logo is a registered
Web Application Hosting in the AWS Cloud Best Practices May 2010 Matt Tavis Page 1 of 12 Abstract Highly-available and scalable web hosting can be a complex and expensive proposition. Traditional scalable
Web Application Hosting in the AWS Cloud Best Practices September 2012 Matt Tavis, Philip Fitzsimons Page 1 of 14 Abstract Highly available and scalable web hosting can be a complex and expensive proposition.
Amazon Web Services Primer William Strickland COP 6938 Fall 2012 University of Central Florida AWS Overview Amazon Web Services (AWS) is a collection of varying remote computing provided by Amazon.com.
Design for Failure High Availability Architectures using AWS Harish Ganesan Co founder & CTO 8KMiles www.twitter.com/harish11g http://www.linkedin.com/in/harishganesan Sample Use Case Multi tiered LAMP/LAMJ
Deploying for Success on the Cloud: EBS on Amazon VPC Session ID#11312 Phani Kottapalli AST Corporation Our Services Oracle Partnership Oracle Specialized E-Business Suite Business Intelligence EPM-Hyperion
Securing the Microsoft Platform on Amazon Web Services Tom Stickle August 2012 (Please consult http://aws.amazon.com/whitepapers/ for the latest version of this paper) Page 1 of 22 Abstract Deploying Microsoft
AVLOR SERVER CLOUD RECOVERY WHITE PAPER 1 Table of Contents Abstract... 2 1. Introduction... 3 2. Server Cloud Recovery... 3 3. Amazon AWS Cloud... 4 a. What it is... 4 b. Why Use AWS?... 5 4. Difficulties
Microsoft SharePoint This topic is 1 of 5 in a series Introduction to Fundamental SharePoint This series is intended to raise awareness of the different fundamental architectural models through which SharePoint
Cloud Computing and Amazon Web Services Gary A. McGilvary edinburgh data.intensive research 1 OUTLINE 1. An Overview of Cloud Computing 2. Amazon Web Services 3. Amazon EC2 Tutorial 4. Conclusions 2 CLOUD
Amazon Web Services 18.11.2015 Yu Xiao Agenda Introduction to Amazon Web Services(AWS) 7 Steps to Select the Right Architecture for Your Web Applications Private, Public or Hybrid Cloud? AWS Case Study
Extend Your IT Infrastructure with Amazon Virtual Private Cloud January 2010 http://aws.amazon.com/vpc Understanding Amazon Virtual Private Cloud Amazon Virtual Private Cloud (Amazon VPC) is a secure and
VMware vcloud Air - Disaster Recovery User's Guide vcloud Air This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition.
Cloud models and compliance requirements which is right for you? Bill Franklin, Director, Coalfire Stephanie Tayengco, VP of Technical Operations, Logicworks March 17, 2015 Speaker Introduction Bill Franklin,
OTM in the Cloud Ryan Haney The Cloud The Cloud is a set of services and technologies that delivers real-time and ondemand computing resources Software as a Service (SaaS) delivers preconfigured applications,
DISASTER RECOVERY WITH AWS Every company is vulnerable to a range of outages and disasters. From a common computer virus or network outage to a fire or flood these interruptions can wreak havoc on your
1. Computation Amazon Web Services Amazon Elastic Compute Cloud (Amazon EC2) provides basic computation service in AWS. It presents a virtual computing environment and enables resizable compute capacity.
Migration Scenario: Migrating Backend Processing Pipeline to the AWS Cloud Use case Figure 1: Company C Architecture (Before Migration) Company C is an automobile insurance claim processing company with
Increased Security, Greater Agility, Lower Costs for AWS DELPHIX FOR AMAZON WEB SERVICES TABLE OF CONTENTS Introduction... 3 Overview: Delphix Virtual Data Platform... 4 Delphix for AWS... 5 Decrease the
Learning Management Redefined Acadox Infrastructure & Architecture w w w. a c a d o x. c o m Outline Overview Application Servers Databases Storage Network Content Delivery Network (CDN) & Caching Queuing
Introduction to AWS Economics Reducing Costs and Complexity May 2015 2015, Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes
Deploying for Success on the Cloud: EBS on Amazon VPC Phani Kottapalli Pavan Vallabhaneni AST Corporation August 17, 2012 Agenda Amazon AWS Global Infrastructure AWS VirtualPrivateCloud(VPC) Architecture
Solution Guide SteelFusion with AWS Hybrid Cloud Storage March 2016 The Challenge According to IDC, to meet the demands of global customer and global talent requirements, companies have to maintain remote
ArcGIS 10.3 Server on Amazon Web Services Copyright 1995-2015 Esri. All rights reserved. Table of Contents Introduction What is ArcGIS Server on Amazon Web Services?............................... 5 Quick
Introduction to Cloud Computing Srinath Beldona firstname.lastname@example.org Agenda Pre-requisites Course objectives What you will learn in this tutorial? Brief history Is cloud computing new? Why cloud computing?
Extending your Enterprise IT with Amazon Virtual Private Cloud Oyvind Roti Principal Solutions Architect, AWS Three Things Some AWS Concepts Let s build a Virtual Private Cloud together Three New Services
MICROSTRATEGY ON AWS Presented by: MicroStrategy World 2015 Tuesday, January 27th 3:30 4:30 PM Track 8 Session 3 WWW.IOLAP.COM 1 INTRODUCTIONS iolap Data Warehousing and Business Intelligence consultancy
CA ARCserve Replication and CA ARCserve High Availability r16 CA ARCserve Replication and CA ARCserve High Availability Deployment Options for Microsoft Hyper-V Server TYPICALLY, IT COST REDUCTION INITIATIVES
Relocating Windows Server 2003 Workloads An Opportunity to Optimize From Complex Change to an Opportunity to Optimize There is much you need to know before you upgrade to a new server platform, and time
Smartronix Inc. Assured Services Commercial Price List Smartronix, Inc. 12120 Sunset Hills Road Suite #600, Reston, VA 20190 703-435-3322 email@example.com www.smartronix.com Table of Contents
Famly ApS: Overview of Security Processes October 2015 Please consult http://famly.co for the latest version of this paper Page 1 of 10 Table of Contents 1. INTRODUCTION TO SECURITY AT FAMLY... 3 2. PHYSICAL
CRM ARCHITECTURAL DESIGNS PAGE 1 Microsoft Dynamics CRM 2013 on Amazon Web Services Microsoft Dynamics CRM 2013 on Amazon Web Services Whitepaper PAGE 3 Abstract This whitepaper is intended for architects
HyperQ DR Replication White Paper The Easy Way to Protect Your Data Parsec Labs, LLC 7101 Northland Circle North, Suite 105 Brooklyn Park, MN 55428 USA 1-763-219-8811 www.parseclabs.com firstname.lastname@example.org
Federal GIS Conference February 9 10, 2015 Washington, DC Using ArcGIS for Server in the Amazon Cloud Bonnie Stayer, Esri Amy Ramsdell, Blue Raster Session Outline AWS Overview ArcGIS in AWS Cloud Builder
Solution Brief: CA ARCserve R16.5 Complexity ate my budget VMware System, Application and Data Availability With CA ARCserve High Availability Adding value to your VMware environment Overview Today, performing
Service Organization Controls 3 Report Report on the Amazon Web Services System Relevant to Security and Availability For the Period April 1, 2015 September 30, 2015 Ernst & Young LLP Suite 1600 560 Mission
Introduction to AWS Security July 2015 Page 1 of 7 Table of Contents Introduction... 3 Security of the AWS Infrastructure... 3 Security Products and Features... 4 Network Security... 4 Inventory and Configuration
WE RUN SEVERAL CRITICAL APPLICATIONS ON AWS BECAUSE WE CAN SCALE AND USE THE INFRASTRUCTURE EFFICIENTLY. - Murari Gopalan Director, Technology Expedia Expedia, a leading online travel company for leisure
Cloud Adoption, Fault Tolerant AWS Support & Magento ecommerce Implementation World s Largest Publisher of Medical and Scientific Literature 1 2013 Compunnel Software Group Cloud Adoption, Fault Tolerant
WHITE PAPER: Egenera Cloud Suite ... Introduction Driven by ever-increasing business demand, cloud computing has become part of many organizations IT strategy today. Driving this transition is the need
WHITE PAPER Software-Defined Networks Powered by VellOS Agile, Flexible Networking for Distributed Applications Vello s SDN enables a low-latency, programmable solution resulting in a faster and more flexible
A Trend Micro Technical White Paper July 2015 Deep Security For Service Providers Deep Security Architecture and Design Paper >> This paper is aimed at service providers that are offering cloud services
Datasheet Cloud Management Cloud Management Overview Meraki s cloud based management provides centralized visibility & control over Meraki s wired & wireless networking hardware, without the cost and complexity