View a markdown version of this page

Considerations for running Oracle E-Business Suite on AWS - Migrating Oracle E-Business Suite on AWS
SizingThroughput requirementsIntegrations with on-premises services

This whitepaper is for historical reference only. Some content might be outdated and some links might not be available.

Considerations for running Oracle E-Business Suite on AWS

There are a number of considerations for running Oracle E-Business Suite on AWS.

Sizing

It is important to right size the Oracle E-Business Suite environment while migrating to AWS, because it can save on infrastructure costs and licensing. Right sizing also gives your business users adequate performance from Oracle E-Business Suite on the cloud.

Migration to the cloud is also an opportunity to fix long-term outstanding issues that you might be having in your current Oracle E-Business Suite environment. Following are a few questions that you should ask your IT team when sizing Oracle E-Business Suite on AWS.

  • When are the peak periods of usage? (such as period close, batch data load, and so on.)

  • What is the pattern of load and spikes on the system? Is it due to transactional or batch load?

  • What is the number of named and concurrent users in the source system and their usage profile?

  • How much business data has to be retained in the system online?

  • What is the percentage of storage growth year-over-year?

  • How many reporting jobs are there? Can those be offloaded to a read-only standby database created using Oracle Active Data Guard?

  • What is the response time requirement from the system?

  • What are the workload requirements from a storage perspective, in terms of peak an average IOPS and throughput?

  • Are there any outliers in terms of jobs/concurrent programs – especially customizations that are causing unnecessary high peaks, and are candidates for tuning?

Getting answers to these questions will help you right size your Oracle E-Business Suite instance, and allow selection of the right deployment topology.

Throughput requirements

Throughput is another important factor when selecting the compute for the database-tier instance. Throughput determines how much data can be read or written to the disk per second by the compute OS. Consider measuring throughput during events such as period end close while multiple concurrent batch jobs are performing intensive read and write operations.

For Oracle RAC workloads, you will have to combine the throughput from all RAC instances when moving to non-RAC based deployment on AWS. Customers can select from a variety of compute instance and storage types that provide highly optimized levels of IOPS and throughput.

Integrations with on-premises services

When migrating Oracle E-Business Suite on AWS, you may have the following integration services:

  • Single sign-on

    • Enterprise-wide single sign-on with Microsoft Active Directory

    • Integration with Okta

  • Microsoft SharePoint

  • Oracle E-Business Suite B2B integration using file-based transfers, such as FTP and HTTP.

  • Integrating with CRM/ERP systems such as Salesforce and SAP.

  • Message queue-based integration using Apache Kafka, IBM MQ, and so on with Oracle E-Business Suite.

Consider the effort involved in services integration, and follow relevant support articles from MyOracleSupport to integrate with these applications and third-party services.