h11209: emc oracle storage connect integration module ... · pdf filethis white paper...

White Paper

EMC Solutions Group

Abstract

This white paper illustrates efficient infrastructure management for a virtualized Oracle E-Business Suite. Enabled by the EMC Oracle VM Storage Connect (OSC) Integration Module with Oracle VM, the management of the EMC Symmetrix VMAX 40K array for test/dev environment provisioning is simplified through a few simple click actions in the Oracle VM Manager console.

March 2013

EMC ORACLE VM STORAGE CONNECT INTEGRATION MODULE ENABLING SIMPLE AND FAST SYMMETRIX VMAX STORAGE ARRAY MANAGEMENT FOR VIRTUALIZED ORACLE E-BUSINESS SUITE EMC Oracle VM Storage Connect Integration Module, EMC Symmetrix VMAX 40k, Oracle E-Business Suite Release 12, and Oracle VM

• Simple storage management • Quick provisioning for Oracle E-Business Suite lifecycle

management • Fully virtualized Oracle E-Business Suite environment using Oracle

VM

EMC Oracle VM Storage Connect Integration Module Enabling Simple and Fast Symmetrix VMAX Storage Array Management for Virtualized Oracle E-Business Suite

2

Copyright © 2013 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided “as is.” EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All trademarks used herein are the property of their respective owners.

Part Number H11209

3 EMC Oracle VM Storage Connect Integration Module Enabling Simple and Fast Symmetrix VMAX Storage Array Management for Virtualized Oracle E-Business Suite

Table of contents

Executive summary ............................................................................................................................... 6 Business case .................................................................................................................................. 6 Solution overview ............................................................................................................................ 6 Key results ....................................................................................................................................... 7

Introduction ......................................................................................................................................... 8 Purpose ........................................................................................................................................... 8 Scope .............................................................................................................................................. 8 Audience.......................................................................................................................................... 8 Terminology ..................................................................................................................................... 8 Oracle VM Storage Connect terminology........................................................................................... 9

Technology overview .......................................................................................................................... 10 Introduction ................................................................................................................................... 10 EMC Symmetrix VMAX 40K ............................................................................................................. 10 TimeFinder/Clone........................................................................................................................... 10 EMC Virtual Provisioning ................................................................................................................ 11 EMC Oracle VM Storage Connect Integration Module ...................................................................... 11 PowerPath...................................................................................................................................... 12 Oracle VM ...................................................................................................................................... 12 Oracle E-Business Suite Release 12 ............................................................................................... 12 Oracle Database 11g Release 2 Enterprise Edition ......................................................................... 12

Solution architecture .......................................................................................................................... 14 Introduction ................................................................................................................................... 14 Solution architecture...................................................................................................................... 14 Solution test scenarios .................................................................................................................. 15

Scenario 1: Initial deployment of Oracle E-Business Suite Release 12 environment ................... 15 Scenario 2: Scaling out of Oracle E-Business Suite Release 12 environment ............................. 15 Scenario 3: Provisioning of Oracle E-Business Suite Test/dev environments ............................. 15

Hardware resources ....................................................................................................................... 16 Virtual machine template configuration ......................................................................................... 17 Software resources ........................................................................................................................ 18 Storage Virtual Provisioning design ................................................................................................ 18 File systems and disk group configuration for the database ........................................................... 19 File system layout for the Oracle E-Business Suite application tier ................................................. 20 File system layout for Oracle E-Business Suite database tier .......................................................... 21 Test bed preparation ...................................................................................................................... 21

Step 1: Install Oracle VM ........................................................................................................... 21 Step 2: Install EMC Oracle VM Storage Connect Integration Module ........................................... 21


4

Step 3: Register the EMC Symmetrix VMAX array on the Oracle VM Manager .............................. 22

Scenario 1: Oracle E-Business Suite Release 12 single-instance configuration .................................. 24 Overview ........................................................................................................................................ 24 Deploy virtual machines ................................................................................................................. 24 Create raw physical disks and present to virtual machines ............................................................. 25 Deploy the Oracle E-Business Suite environment ........................................................................... 26

Scenario 2: Scaling out Oracle E-Business Suite Release 12 environment .......................................... 27 Overview ........................................................................................................................................ 27 Deploy virtual machines ................................................................................................................. 27 Create shared raw physical disks ................................................................................................... 28 Scale database and application tiers to multinode......................................................................... 29

Scenario 3: Provisioning Oracle E-Business Suite test/dev environment ............................................ 31 Overview ........................................................................................................................................ 31 Test objective ................................................................................................................................. 31 Test scenario.................................................................................................................................. 31 Test procedure ............................................................................................................................... 32

Building the performance baseline ............................................................................................ 32 Provision test/dev environments ............................................................................................... 32

Test results .................................................................................................................................... 33 O2C online workload ................................................................................................................. 34 O2C batch workload .................................................................................................................. 35

Conclusion ......................................................................................................................................... 38 Summary ....................................................................................................................................... 38 Findings ......................................................................................................................................... 38

References ......................................................................................................................................... 40 White papers ................................................................................................................................. 40 Product documentation .................................................................................................................. 40 Other documentation ..................................................................................................................... 40

Supporting information ...................................................................................................................... 42 Introduction ................................................................................................................................... 42 OASB O2C online workload ............................................................................................................ 42

OM_Insert_Order (OMIO) ........................................................................................................... 42 OM_Order_Pick_Release (OMPR) ............................................................................................... 42 OM_Ship_Confirm (OMSC) ........................................................................................................ 42 AR_Invoice_Manual_Insert (ARIMI) ............................................................................................ 42 OM_Order_Summary_Report (OMOSR) ...................................................................................... 43 AR_Customer_Summary (ARCS) ................................................................................................. 43


O2C batch workload ....................................................................................................................... 43


6

Executive summary

Oracle E-Business Suite is a sophisticated enterprise business application suite featuring Application Lifecycle Management (ALM) for handling repetitive provisioning tasks for development, production, test, and maintenance environments over an Oracle E-Business Suite application lifetime.

A deployed Oracle E-Business Suite infrastructure must be efficient to reduce cost and achieve resource optimization for the Oracle ALM tasks. Oracle E-Business Suite administration and development teams are increasingly under pressure to become agile and deploy new environments quickly, to scale out the existing Oracle E-Business Suite environments, and to quickly and reliably provision new test and development Oracle E-Business Suite environments without affecting the Oracle E-Business Suite production environment.

This solution describes an Oracle E-Business Suite environment virtualized with Oracle VM deployed on an EMC Symmetrix 40K array. The EMC OSC Integration Module enables the integration of the hypervisor, virtual machines, and the VMAX 40K array, providing efficient storage management in the Oracle VM virtualization environment. The main components of the solution are:

• EMC Symmetrix VMAX 40K builds on EMC’s industry-leading Symmetrix storage array platform for powerful, trusted, smart storage that provides higher levels of performance, availability, and intelligence in the virtual data center.

• The EMC OSC Integration Module is built on the Oracle VM Storage Connect framework. It implements a full set of OSC APIs for discovering and provisioning EMC Symmetrix storage arrays. By enabling this module in Oracle VM, customers can perform the storage management tasks on the Oracle VM Manager for the Oracle E-Business Suite environment.

• Oracle VM provides virtualized infrastructure for the Oracle E-Business Suite application and database tiers.

This solution demonstrates the EMC OSC Integration Module for Oracle VM, illustrating tight integration between the Oracle VM and underlying EMC Symmetrix VMAX storage array. The EMC OSC Integration Module for Oracle VM enables the following accelerated administration tasks directly from the Oracle VM Manager interface:

• Virtual machine deployment

• Raw physical disk creation

• Raw physical disk cloning

This agility facilitates efficient virtualized Oracle E-Business Suite infrastructure management. This technology stack in turn accelerates management tasks in the Oracle E-Business Suite application lifecycle, including:

• Initial Oracle E-Business Suite deployment

• Oracle E-Business Suite scale-out

• Rapid Oracle E-Business Suite environment provisioning (Test/Dev/Path/etc.)

Business case

Solution overview


This solution demonstrates the following:

• Performance – A fast and easy way to deploy new Oracle E-Business Suite environments, scale out the existing environment, and provision test/dev environments.

• Resiliency – Minimal performance impact on the existing production environment during the test/dev environment provisioning

• Agility – Multiple Oracle E-Business Suite test/dev environments provisioning in an efficient and agile way using EMC OSC Integration Module.

• Efficiency – Optimal implementation and configuration details to achieve the benefits of Oracle Real Application Clusters (RAC) and Oracle VM for Oracle E-Business Suite Release 12 applications.

Key results


8

Introduction

This white paper describes how to efficiently manage the underlying infrastructure of the Oracle E-Business Suite using an EMC VMAX storage array, Oracle VM, and EMC Oracle VM Storage Connect Integration Module. It also validates that the test/dev environment provisioning operations do not compromise the availability of the corresponding E-Business Suite production environment and only minimally impact on the performance.

The scope of the white paper is to:

• Introduce the key solution technologies

• Describe the solution architecture and design

• Describe the steps involved in managing the infrastructure of the Oracle E-Business Suite and its application lifecycle

• Compare the performance statistics to validate the performance impact induced by the test/dev environment provisioning operations

• Identify the key business benefits of the solution

This white paper is intended for chief information officers (CIOs), data center directors, Oracle database and application administrators, storage administrators, system administrators, virtualization administrators, technical managers, and any others involved in evaluating, acquiring, managing, operating, or designing Oracle E-Business Suite environments.

This paper includes the terminology defined in Table 1.

Table 1. Terminology

Acronym Term

FC Fibre Channel

LUN Logical unit number

NIC Network interface card

NFS Network File System

ODM Oracle Disk Manager

OLTP Online transaction processing

RAC Real Application Clusters

SAS Serial Attached SCSI

SCSI Small Computer System Interface

SGA System global area

TPM Transactions per minute

OATS Oracle Application Testing Suite

Purpose

Scope

Audience

Terminology


Acronym Term

OASB Oracle Application Standard Benchmark

O2C Order to Cash

OSC EMC Oracle VM Storage Connect Integration Module

Table 2 provides Oracle VM terms used in this white paper:

Table 2. Oracle VM Storage Connect terminology

Term Definition

Raw physical disk The raw physical disk is the LUN created from the Oracle VM volume group and accessed directly by the virtual machine

Volume group The virtual pool (for thin device created only) created from the Symmetrix array

Access group The equivalent of an access group is a Symmetrix initiator group, which includes a list of host initiator WWNs. It controls whether a raw physical disk can be accessed by a virtual machine or not.

Oracle VM Storage Connect terminology


10

Technology overview

The solution uses the following hardware and software components:

• EMC Symmetrix VMAX 40K

• EMC Oracle VM Storage Connect Integration Module

• PowerPath

• Oracle VM

• Oracle Database 11g Release 2 Enterprise Edition with Oracle Real Application Clusters (RACs)

• Oracle E-Business Suite Release 12

• Oracle Application Testing Suite

• Oracle Application Standard Benchmark Toolkit

The EMC Symmetrix VMAX 40K builds on EMC’s industry-leading Symmetrix storage array platform for powerful, trusted, smart storage that provides higher levels of performance, availability, and intelligence in the virtual data center.

Designed to enable the hybrid cloud, Symmetrix VMAX 40K and the Enginuity 5876-operating environment offer management automation and data mobility technologies that are critical to the delivery of cloud-based infrastructure and IT services. The Enginuity 5876 technology for networking, sharing, and tiering storage helps data centers consolidate applications and deliver new efficiency levels through higher utilization rates, improved mobility, and simplified storage management.

Built on the strategy of simple, intelligent, and modular storage, the VMAX 40K incorporates a highly scalable virtual matrix architecture that enables Symmetrix VMAX arrays to grow seamlessly and cost-effectively from an entry-level configuration into the world’s largest storage system. Symmetrix VMAX supports Flash drives, Fibre Channel (FC) drives, and Near-Line SAS (NL-SAS) drives within a single array, as well as an extensive range of RAID types. The EMC Symmetrix VMAX 40K provides the performance and mission-critical availability to address the challenges of enterprise IT systems to support both online and batch workload.

TimeFinder/Clone provides point-in-time copies of devices that you can use for backups, decision support, data warehouse refreshes, or any other processes that require parallel access to production data.

TimeFinder/Clone allows you to make data copies simultaneously on multiple target devices from a single source device. The data is copied from the source device, creating a physical backup copy called a clone. The data is available to a target device’s host immediately upon activation of the TimeFinder copy session, even if the copy process has not completed.

TimeFinder/Clone copies are appropriate in situations where multiple copies of production data are needed for recovery, testing, backup, or report generation. Using

Introduction

EMC Symmetrix VMAX 40K

TimeFinder/Clone


clone copies can reduce disk contention and improve data access speed by assigning users to clones rather than to the production data.

EMC Virtual Provisioning simplifies storage management, improves capacity utilization, and enhances performance. Virtual Provisioning provides the separation of physical storage devices from the storage devices as perceived by the host system.

Virtual Provisioning introduces the following concepts and components:

• Thin devices are devices that do not have storage allocated to them when they are created. Thin devices can be created with an inflated capacity, because data devices provide the actual storage space for data written to them. To a host operating system, thin devices look like regular devices with their configured capacity, and the host interacts with them in the same way as with regular devices.

• Data devices are special devices (not mapped to the host) that provide physical storage for thin devices. Data devices must be enabled in a virtual pool before they can be used.

• A virtual pool is a collection of data devices that provides storage capacity for the thin devices that are bound to the pool. All data devices in a given virtual pool share the same RAID protection type and are of the same drive technology.

Figure 1 depicts the relationship between thin devices and their associated thin pool.

Figure 1. Thin devices and thin pools containing data devices

The EMC Oracle VM Storage Connect Integration Module enables Oracle VM Manager to discover and provision EMC Symmetrix VMAX storage arrays. The Integration Module is built upon the OSC framework, which provides a set of storage discovery and provisioning Application Programming Interfaces (APIs) that enhance the ability to manage and provision storage devices in an Oracle VM environment.

EMC Virtual Provisioning

EMC Oracle VM Storage Connect Integration Module


12

EMC OSC Integration Module supports the following storage management and provisioning operations for EMC Symmetrix VMAX storage arrays:

• LUN discovery and inquiry

• Thin LUN creation and removal

• Auto-provisioning (LUN masking)

• Clone device creation and removal

The EMC OSC Integration Module depends on EMC SMI-S Provider, which supports the SNIA Storage Management Initiative (SMI), an ANSI standard for storage management.

EMC PowerPath is host-based software that provides automated data path management and load-balancing capabilities for heterogeneous servers, networks, and storage deployed in physical and virtual environments. With PowerPath, a server node can access the same storage area network (SAN) volume via multiple paths (HBA ports), which enables both load balancing across the multiple paths and transparent failover between the paths. PowerPath offers significant benefits for the high-throughput requirements of enterprise Oracle environments. It enables you to:

• Standardize data path management across physical and virtual environments and manage growth without purchasing more infrastructure components.

• Automate multipathing policies and load balancing to provide predictable and consistent database availability.

• Improve service-level agreements by eliminating application impact from I/O failures.

Oracle VM is a server virtualization solution composed of Oracle VM Server for x86 and Oracle VM Manager. Oracle VM Server is composed of a hypervisor and a privileged domain (Dom0) that allows multiple domains or virtual machines (such as Linux, Solaris, and Windows) to run on one physical machine. Oracle VM Manager controls the virtualization environment by creating and monitoring Oracle VM servers and virtual machines.

Oracle E-Business Suite is a suite of business applications developed by Oracle. Oracle E-Business Suite Release 12 provides organizations of all sizes, across all industries and regions, with a global business foundation that reduces costs and increases productivity through a portfolio of rapid value solutions, integrated business processes, and industry-focused solutions.

Oracle Database 11g Release 2 Enterprise Edition delivers industry-leading performance, scalability, security, and reliability on a choice of clustered or single servers running Windows, Linux, or UNIX. It provides comprehensive features for transaction processing, business intelligence, and content management applications. This solution implements many Oracle Database11g R2 features including RAC and Automatic Storage Management (ASM). In Oracle 11g R2, Oracle ASM and Oracle Clusterware have been integrated into the Oracle Grid Infrastructure.

PowerPath

Oracle VM

Oracle E-Business Suite Release 12

Oracle Database 11g Release 2 Enterprise Edition


This provides the cluster and storage services required to run Oracle RAC databases. Oracle ASM is also extended to store Oracle Cluster Registry (OCR) and voting disks.


14

Solution architecture

This solution details the application lifecycle management of Oracle VM virtualized Oracle E-Business Suite Release 12 on an EMC Symmetrix VMAX 40K array. It includes the following scenarios:

• Initial deployment of the E-Business Suite production environment

• Scaling out the existing E-Business Suite production environment

• Fast provisioning of E-Business Suite test/dev environments

Figure 2 depicts the architecture of this solution. An Oracle VM server farm with two Oracle VM servers and the Symmetrix VMAX 40K storage array provide the infrastructure for the Oracle E-Business Suite environment. The physical servers connect to the Symmetrix VMAX 40K storage via Fibre Channel (FC) storage attached network (SAN). The physical servers connect to each other using 10GbE network.

Figure 2. Architecture overview

Introduction

Solution architecture


This section defines three test scenarios designed to validate the performance of the documented solution.

Scenario 1: Initial deployment of Oracle E-Business Suite Release 12 environment

In this scenario, we1 created two virtual machines and multiple raw physical disks, and then deployed the OASB kit on this infrastructure. The benchmark, provided by Oracle Corporation, is referred to as the Oracle Application Standard Benchmark (OASB). It generates a comparable standard workload which demonstrates the performance and scalability of Oracle E-Business Suite and provides metrics for the comparison of Oracle E-Business Suite performance on different system configurations. The OASB kit consists of a single application node and a single-instance database node.

Scenario 2: Scaling out of Oracle E-Business Suite Release 12 environment

In this scenario, we created two virtual machines and multiple raw physical disks, and then scaled out the existing single application node and single instance database node Oracle E-Business Suite environment to a two application nodes and two-node RAC database Oracle E-Business Suite environment.

Scenario 3: Provisioning of Oracle E-Business Suite Test/dev environments

In this scenario, we provisioned the single application node and single-instance database node test/dev Oracle E-Business Suite environment by cloning the two-application node and two-node RAC database production environment. We also validated the performance impact of the provisioning operations on the production environment by running the OASB workload on it and comparing the performance metrics.

In this solution, we used the benchmark components to measure the O2C (both online and batch) business processes response time for extra-large database model. We conducted the testing in a controlled environment with no other applications running. The OATS runtime environment, which was included in the OASB toolkit, was used for generating the O2C online workload by simulating concurrent users.

Figure 3 depicts the evolution of the underlying infrastructure for each scenario.

1 In this white paper, “we” refers to the EMC solutions engineering team that deployed and validated the solution.

Solution test scenarios


16

Figure 3. Infrastructure evolution of each scenario

Table 3 details the hardware resources for this solution.

Table 3. Hardware resources

Purpose Quantity Configuration

Storage array 1 EMC Symmetrix VMAX 40K with:

Enginuity 5876

4 engines, 128 GB cache each

66 x 450 GB 10K 3.5” FC drives

39 x 2 TB 7.2K 3.5” NL-SAS drives

Hardware resources


Purpose Quantity Configuration

Oracle VM server

2 4 x 8-core CPUs,

128 GB RAM,

2 x Dual-port 1 Gb/s Ethernet NICs

2 x Dual-port 10 Gb/s CNA NICs

2 x Dual-port 8 Gb/s FC HBAs

SAN switch 2 8 Gb/s FC switches

Ethernet switches

2 10 Gb/s Ethernet switches (for private interconnect)

2 1 Gb/s Ethernet switches (for public network)

Table 4 lists the configuration of virtual machines used for the Oracle E-Business Suite application tier.

Table 4. Virtual machine used for the Oracle E-Business Suite application tier

Part Description

CPU 24 vCPUs

Memory 60 GB

Operating system Oracle Linux 5.6

Kernel 2.6.32-300.3.1.el6uek.x86_64

Virtualization mode Paravirtualized

Network interfaces Eth0: public/management IP network

OS users Username: oracle and applmgr

OS groups Group: oinstall, dba and apps

RPM packages installed (as Oracle prerequisites)

Refer to the Oracle installation guide.

System configuration (as Oracle prerequisites)

See the Oracle Installation Guide.

Table 5 lists the configurations of virtual machines used for the Oracle E-Business Suite database tier.

Table 5. Virtual machine used for the Oracle E-Business Suite database tier

Part Description

CPU 30 vCPUs

Memory 30 GB

Operating system Oracle Linux Server release 5.6

Kernel 2.6.32-300.3.1.el6uek.x86_64

Virtualization mode Paravirtualized

Virtual machine template configuration


18

Part Description

Network interfaces Eth0: public/management IP network

Eth1 (10 Gb): dedicated to cluster interconnect

OS users Username: oracle and applmgr

OS groups Group: oinstall, dba and apps

RPM packages installed (as Oracle prerequisites)

Refer to the Oracle installation guide.

System configuration (as Oracle prerequisites)

See the Oracle Installation Guide.

Table 6 details the software resources for the solution.

Table 6. Software resources

Software Version Purpose

VMAX Enginuity code 5876 VMAX Enginuity

EMC Solutions Enabler 7.5 Host CLI storage management software

EMC SMI-S Provider 4.4.0.1 Windows x64 The SMI-S provider

EMC PowerPath 5.7 SPE Multipathing and load balancing software

EMC Oracle VM Storage Connect Integration Module

1.1 A plug-in installed on the Oracle VM servers to enable the storage management on Oracle VM Manager

Oracle Grid Infrastructure Enterprise Edition 11.2.0.3

Clusterware and ASM software

Oracle Database Enterprise Edition 11.2.0.3

Oracle database software

Oracle Linux 5.6 Production and backup host operating system

Microsoft Windows 2008 R2 Operating system of the storage management server

Oracle VM 3.1.1 Oracle Virtual Machine

Oracle E-Business Suite 12.1.3 Oracle E-Business Suite applications

Oracle Application Test Suite

9.3.1 Production Order to Cash (O2C) online workload generator

EMC Virtual Provisioning automatically stripes data across all data devices in a virtual pool, and balances the utilization across storage devices. To ensure even striping of data, EMC recommends that all data devices in a virtual pool are of the same size.

Software resources

Storage Virtual Provisioning design


Table 7 shows the RAID protections, drive types, usage, and the configuration for each virtual pool. In this solution, Oracle datafiles, redo log files, and temporary files were located on the thin devices using RAID 1 protection for the best performance. We used 7.2K NL-SAS drives with RAID 6 protection for Flash Recovery Area (FRA) files, which were less sensitive to performance.

Table 7. Virtual pool design on Symmetrix VMAX 40K

Virtual pool/volume group

RAID protection

Drive type

Usage Configuration

15K_FC_pool RAID 1 FC 15K VM OS/template files

Oracle VM Storage Repository

Oracle E-Business Suite APPL_TOP

Raw physical disk configured as ext3 file system

Oracle binaries (database and grid infrastructure)

Raw physical disks configured as ext3 file system

CRS Raw physical disks configured as ASM disks

DATA Raw physical disks configured as ASM disks

REDO Raw physical disks configured as ASM disks

NL_SAS_pool RAID 6 (6+2)

NL-SAS 7.2K

FRA Raw physical disks configured as ASM disks

In the initial deployment, we stored the database files of the single-instance database on an ext3 file system.

Table 8 details the configuration of the file system.

Table 8. Configuration of the file system

Item Raw physical disk size (GB)

File system name Virtual pool

DATA 1024 /u01/oracle/VIS/db/apps_st/data 15K_FC_pool

When converting the single-instance database to the two-node RAC database, we migrated the database files on the file system to the ASM disk group of the RAC database.

Table 9 details the ASM disk group design for the two-node RAC database. We used three ASM disk groups with external redundancy to store relevant database files.

We placed the:

• Datafiles, control files, and temporary files in the +DATA disk group.

File systems and disk group configuration for the database


20

• CRS and voting disk files in the +CRS disk group.

• Archived redo log files in the +FRA disk group.

• Online redo log files in the +REDO1 and +REDO2 disk groups, which were used by two instances respectively.

Note Migrating the database files, which were previously placed on the file system, to ASM disk groups afterward is a common practice in actual deployments.

Table 9. ASM disk group design

Item Raw physical disk size (GB)

Number of raw physical disks

ASM disk group name

Virtual pool

DATA 1024 2 +DATA 15K_FC_pool

FRA 1024 1 +FRA NL_SAS_pool

CRS 10 5 +CRS 15K_FC_pool

REDO 100 2 +REDO1 15K_FC_pool

REDO 100 2 +REDO2 15K_FC_pool

During the rapid test/dev environment provisioning, we created clones of the production environment’s ASM disk groups +DATA, +REDO1, +REDO2, and +FRA and presented them to the test/dev database virtual machine.

Table 10 details the configuration of the single-instance database’s ASM disk group in the test/dev environment.

Table 10. ASM disk group configuration

Item

Raw physical disk size (GB)

Number of raw physical disks

ASM disk group name

Virtual pool Note

DATA 1024 2 +DATA 15K_FC_pool Clone

REDO 100 2 +REDO1 15K_FC_pool Newly created

REDO 100 2 +REDO2 15K_FC_pool Newly created

FRA 1,024 1 +FRA NL_SAS_pool Clone

Table 11 provides an overview for the file system layout of the Oracle E-Business Suite Release 12 application tier.

Table 11. Oracle E-Business Suite Release 12 file system application tier layout

File system Path

COMMON_TOP /u02/applmgr/VIS/apps/apps_st/comn

APPL_TOP /u02/applmgr/VIS/apps/apps_st/appl

File system layout for the Oracle E-Business Suite application tier


File system Path

OracleAS 10.1.2 ORACLE_HOME /u02/applmgr/VIS/apps/tech_st/10.1.2

OracleAS 10.1.3 ORACLE_HOME /u02/applmgr/VIS/apps/tech_st/10.1.3

INST_TOP /u01/applmgr/VIS/inst/apps/VIS_app1

We installed the application node technology stack— APPL_TOP, OracleAS 10.1.2 ORACLE_HOME, and OracleAS 10.1.3 ORACLE_HOME— on the ext3 file system created from the raw physical disk. In the two-node Oracle E-Business Suite application tier configuration, we exported the ext3 file system on the first node to the second node as an NFS file system.

Table 12 provides an overview of the file system layout of the Oracle E-Business Suite Release 12 database tier.

Table 12. Oracle E-Business Suite Release 12 file system database tier layout

File system Path

GRID_HOME /u01/app/11.2.0/grid

ORACLE_HOME /u01/app/oracle/product/11.2.0/db_1

We installed GRID_HOME and ORACLE_HOME on the ext3 file system created from the separated raw physical disks and mounted them to each virtual machine.

This section describes the steps necessary to prepare the test bed.

Step 1: Install Oracle VM

Oracle VM Server for x86 is an Oracle server virtualization platform that makes enterprise applications easier to deploy and manage. The Oracle virtual machine environment consists of one or more Oracle VM servers that are grouped into a server pool and managed by Oracle VM Manager. Oracle VM Server enables hardware resources (CPUs, memory, networks, and storage) to become flexible resource pools from which to build virtual machines.

In Oracle VM, Oracle VM Server is a central component that includes a virtual machine agent started after the successful installation of the Oracle VM server. The agent enables the communication channel with the Oracle VM Manager, which provides a graphical interface for creating and managing the virtual infrastructure. In this solution, we configured an Oracle VM server farm consisting of two Oracle VM servers.

Refer to the document entitled Oracle VM Installation and Upgrade Guide for detailed installation guidelines of Oracle VM Server and Oracle VM Manager.

Step 2: Install EMC Oracle VM Storage Connect Integration Module

EMC Oracle VM Storage Connect Integration Module integrates with Oracle VM to provide an easy way to manage the EMC VMAX array including raw physical disk creation, cloning, and other tasks.

File system layout for Oracle E-Business Suite database tier

Test bed preparation


22

Before managing the array, we installed the EMC OSC Integration Module in the Oracle VM servers. The Module is released as a RPM package and downloadable from EMC Powerlink available to customers and partners at: EMC Oracle VM

. Storage

Connect Integration Module V1.1

To install the EMC OSC Integration Module, we logged in using the root account on the Oracle VM server, and ran the rpm command as shown in Figure 4. All installed files were in the directory /opt/storage-connect/plugins/emc/. The Module does not have log files of its own. All log messages are stored in the Oracle VM Agent log file, /var/log/ovs-agent.log.

Figure 4. Installing the EMC OSC Integration Module on the Oracle VM server

Step 3: Register the EMC Symmetrix VMAX array on the Oracle VM Manager

After installing the Module, we registered the EMC Symmetrix array to the Oracle VM Manager. This step is needed to logically identify the Oracle VM server and the array to each other in the Oracle VM Manager, as shown in Figure 5.

Figure 5. Logically identify Oracle VM Server and the Symmetrix array

We then used Access Group to make the raw physical disk accessible to the Oracle VM server, as shown in Figure 6.

http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Software_Download/osc-emc-isa-1.1.0.1-1.el5.x86_64.rpm�

http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Software_Download/osc-emc-isa-1.1.0.1-1.el5.x86_64.rpm�


Figure 6. Creating the Oracle VM Access Group


24

Scenario 1: Oracle E-Business Suite Release 12 single-instance configuration

In this solution, we deployed all Oracle E-Business Suite application and database tiers on an Oracle VM farm consisting of two Oracle VM servers. We installed the Oracle VM servers with EMC OSC Integration Module, which enabled the storage management on the Oracle VM Manager.

In this scenario, we:

• Created two virtual machines using an Oracle VM template

• Created multiple raw physical disks from the Oracle VM volume group and mounted them to the virtual machines.

• Installed the Oracle OASB benchmark kit on the newly created infrastructure

• Configured the Oracle VM volume group on the virtual pool in the EMC VMAX array

• Clicked on the Oracle VM Manager console to create a raw physical disk and thin devices /LUNs from the virtual pool in the VMAX array. The thin devices did not require pre-allocated physical storage at the time we created the device and presented it to the virtual machine. When a write was performed to a part of any thin device for which physical storage had not yet been allocated, the EMC Symmetrix allocated physical storage from the virtual pool for the portion of the thin device only. This approach reduces the amount of storage that is actually consumed and provides better storage utilization.

On the Oracle VM Manager console, we created two virtual machines from the template in the Oracle VM server farm to use the Xen PVM (paravirtualized machine) domain type as shown in Figure 7.

Figure 7. Deploying new virtual machines

Overview

Deploy virtual machines


Note Xen supports a form of virtualization known as paravirtualization, in which guests run a modified operating system. Through paravirtualization, Xen can achieve high performance even on its host architecture (x86), which has a reputation for non-cooperation with traditional virtualization techniques.

With the EMC OSC Integration Module on the Oracle VM servers, we created the necessary raw physical disks and presented them to the virtual machines using the Oracle VM Manager through the following steps:

1. Created raw physical disks from the Oracle VM volume group as shown in Figure 8.

Figure 8. Creating the raw physical disks

We created two types of raw physical disks: one for the database files, and the other for the application binaries and database/grid infrastructure binaries.

2. We presented the raw physical disks to the virtual machines as shown in Figure 9.

Figure 9. Presenting the raw physical disks

Create raw physical disks and present to virtual machines


26

After presenting the raw physical disks to the virtual machines, we formatted all of the raw physical disks as ext3 file systems.

The OASB kit includes the Oracle E-Business Suite application and the Oracle database. The application in the kit contains a full set of components that are necessary to run the Oracle E-Business Suite. The Oracle database in the kit contains all the binaries and database files with pre-populated data, which are necessary to run as a single-instance database.

To build the Oracle E-Business Suite Release 12 production environment using the OASB Toolkit, we:

1. Uncompressed the files of the kit to each virtual machine, and then ran the Rapid Clone scripts. The initial Oracle E-Business Suite environment deployed from the OASB kit consists of a one-node application tier and a one-node database tier.

2. Set the initial parameters for Oracle Application Release 12 database.

3. Configured the FORM and OACORE Java virtual machines on the application tier.

Deploy the Oracle E-Business Suite environment


Scenario 2: Scaling out Oracle E-Business Suite Release 12 environment

To emulate the real-world business environment, this solution extends the single application node and single-instance database Oracle E-Business Suite production environment into two application nodes and two-node RAC database configuration:

• Database tier: Convert the single-instance to the two-node RAC database using ASM.

• Application tier: Convert the single application node to the two-node application tier with a shared file system. One of the nodes acts as an NFS server, sharing the APPL_TOP file system with the other application nodes.

This scenario shows how to scale out the database and application tiers.

On the Oracle VM Manager console, we created two virtual machines from the template, adding one of them to the application tier, and the other to the database tier. The newly created virtual machines, together with the virtual machine in the existing environment, made up a two-node application and two-node RAC database Oracle E-Business Suite environment, as shown in Figure 10.

Figure 10. Deploying virtual machines

Overview

Deploy virtual machines


28

The database files of the single-instance database were stored on the ext3 file system, which was not a shared file system. In order to scale out the single-instance database to a two-node RAC database using ASM as the shared storage, we created multiple raw physical disks shared between Oracle VM servers from the Oracle VM volume group. On the Oracle VM Manager, we created the raw physical disks with the Shareable checkbox selected, which indicates that the Oracle VM servers in the Oracle VM farm will share this raw physical disk.

To create the shared raw physical disks, we:

1. Selected Shareable option as shown in Figure 11.

Figure 11. Creating shared raw physical disks

2. We presented the raw physical disks to the virtual machine of the database tier as shown in Figure 12.

Figure 12. Presenting the shareable raw physical disks to the virtual machines

Create shared raw physical disks


As shown in Figure 13, the disk information indicates whether the disk is shareable or not. The servers where the raw physical disks are presented are also displayed in the Oracle VM Manager console.

Figure 13. Displaying the raw physical disks on the Oracle VM Manager console

Table 13 lists the raw physical disks created and their configurations.

Table 13. Raw physical disks configurations

Name Number Configuration Shareable Usage

DATA 2 ASM disk YES Mount to both nodes, used for datafiles, temp files, control files

REDO 4 ASM disk YES Mount to both nodes, used for online redo log files

CRS 5 ASM disk YES Mount to both nodes, used for CRS and voting disk files

FRA 1 ASM disk YES Mount to both nodes, used for archived redo log files

ORA_bin1 1 Ext3 filesystem NO Mount to the first node, used for the database binaries

ORA_bin2 1 Ext3 filesystem NO Mount to the second node, used for the database binaries

Grid_bin1 1 Ext3 filesystem NO Mount to the first node, used for the oracle grid infrastructure binaries

Grid_bin2 1 Ext3 filesystem NO Mount to the second node, used for the grid infrastructure binaries

Once all necessary raw physical disk virtual machines and shared raw physical disks were ready, we converted the initial single-instance Oracle E-Business Suite environment to the two-node application tier and the two-node RAC database tier. During the database conversion, the database files, which were previously stored on the file system of single-instance database, were migrated to the ASM disk groups of the two-node RAC database. We used the software-based (Apache) Load Balancer on top of the two application tier nodes and server-side load balance on the database nodes to provide load balancing for the environment.

Scale database and application tiers to multinode


30

Figure 14 shows the configuration of the two-node RAC database:

Figure 14. Configuring the two-node RAC database

Refer to the sections entitled File systems and disk group configuration for the database and File system layout for the Oracle E-Business Suite application tier for further details about the file systems related to the database and application tiers.


Scenario 3: Provisioning Oracle E-Business Suite test/dev environment

In this scenario, we ran the OASB workload on the production environment and captured the performance statistics as the baseline. We then provisioned the test/dev Oracle E-Business Suite environment with the same OASB workload running on the production environment at the same time. We captured the performance statistics and compared them to the baseline, validating the performance impact of the provisioning operations.

Enabling EMC Oracle VM Storage Connect Integration Module on the Oracle VM server simplifies the management of the EMC VMAX storage array. Customers can create multiple copies of the Oracle E-Business Suite production environment including the application tier and the database tier, and then repurpose these copies for test/dev systems, and other purposes. Provisioning the test/dev environment mainly relies on the TimeFinder/Clone technology in the VMAX array, which allows you to clone copies of data simultaneously on multiple target devices from a single source device, making the data available to a target’s virtual machine device instantly (the device is the equivalent of a raw physical disk in Oracle VM). When clicking on the Oracle VM Manager console to clone a raw physical disk, TimeFinder/Clone initiates, which establishes the clone pair in the array and creates a point-in-time copy of the source raw physical disk.

In this scenario, we not only cloned the raw physical disk of the ASM disk groups, but also cloned the raw physical disks for the application binaries, database binaries, and grid infrastructure binaries. Thus, there was no need to install the binaries on the target virtual machines, which greatly reduced provisioning time.

This scenario demonstrates non-disruptive provisioning of the test/dev and non-production environment by initiating EMC Symmetrix VMAX storage cloning and Oracle VM template deployment on the Oracle VM Manager console. This test demonstrates, for the application and database architects, how EMC technology with Oracle VM can accelerate the Oracle E-Business Suite application lifecycle management by provisioning more than two test/dev environments.

This section describes how to the provision test and development environments by deploying new virtual machines and cloning the raw physical disks of the production environment using the Oracle VM Manager console. To complete this scenario, we performed the following steps:

• Baseline the performance by running the workload, which consists of O2C online and batch workloads on the production environment. We captured the results and used them as a performance baseline for further comparison. To obtain these results:

The OATS tool generated the O2C online workload on the production environment with 1,190 virtual users.

The O2C batch workload was initiated from a benchmark-provided SQL script to process 50,000 order lines.

• Provisioned the test/dev environments by deploying on the Oracle VM Manager console two virtual machines from the template, and cloned the raw physical

Overview

Test objective

Test scenario


32

disks of the production environment while the same workload was running on the production environment. We captured the performance data and compared it with the baseline to validate the performance impact on the production environment.

Building the performance baseline

To simulate a real-world case and create a performance baseline, we ran the OASB O2C workload.

Provision test/dev environments

To provision test/dev environments, we:

1. Ran the same OASB O2C workload on the production environment.

2. On the Oracle VM Manager console, deployed two virtual machines from the template, which we used as the application node and the database node of the test/dev environment. Refer to the section entitled Deploy virtual machines for details.

3. Ran the Oracle E-Business Suite adpreclone.pl script on the application and database nodes.

4. On the Oracle VM Manager, cloned the raw physical disks of the production environment and presented and mounted them to the newly deployed virtual machines as shown in Figure 15. Refer to the section entitled Create raw physical disks and present to virtual machines for details.

Figure 15. Raw physical disk cloning

We performed the following steps to clone the raw physical disks of the production Oracle E-Business Suite environment:

1. Cloned the raw physical disk that was used for the shared APPL_TOP on the application tier.

2. Cloned the raw physical disks that were used for the Oracle database and grid infrastructure binaries.

3. On the production environment:

Test procedure


a. Ran the SQL in the SQLPLUS:

alter database begin backup;

b. On the Oracle VM Manager, cloned the raw physical disks of the ASM disk group +DATA.

c. Ran the SQL in the SQLPLUS:

alter database end backup;

d. Ran the SQL in the SQLPLUS:

alter system archive log current;

e. On the Oracle VM Manager, cloned the raw physical disk of the ASM disk group +FRA.

f. Made a copy of the control file by running the following SQL command in SQLPLUS:

alter database backup controlfile to trace;

then sent the controlfile script to the test/dev environment and customized it.

4. Created four raw physical disks from the Oracle VM 15K_FC volume group and presented them to the database node of the test/dev environment. We configured them as ASM disks, and created two ASM disk groups (+REDO1, +REDO2), with two ASM disks in each disk group.

5. On the database node of the test/dev environment, rescanned the ASM disks and configured the Oracle grid infrastructure and database binaries to the standalone server mode, then completed the following steps:

a. Started up the database with the nomount option.

b. Ran the modified backup control file script to recreate the controlfile.

c. Made a point-in-time recovery by running the following SQL command on SQLPLUS:

recover database until cancel using backup controlfile;

d. Opened the database for access.

6. Followed the Oracle E-Business Suite Rapid Clone process to provision the test/dev environments.

7. Gathered the performance statistics of the O2C OASB workload.

Figure 16, Figure 17, and Figure 18 show the performance impact of the cloning operations on the production environment, in comparison with the baseline. We obtained all the performance statistics shown in this section by running multiple rounds of testing and averaging the statistics captured. We collected the O2C online workload performance statistics from the session report of the Oracle Load Testing console, and the O2C batch workload performance statistics by running the script provided in the OASB kit.

Test results


34

The following sections describe the results of each test.

O2C online workload

Figure 16 and Figure 17 show the average response time and 90th percentile response time of each online profile between the baseline testing and the provisioning testing.

• The average response time is the average performance of all the virtual users.

• The 90th percentile response time is the average performance of 90 percent of the virtual users.

Note The OATS response time is server response time and does not include browser rendering or other realworld real user time. And the 90th percentile response time is an important metric to evaluate the performance of the Oracle E-Business Suite system’s online workload. It shows the average response time that 90 percent of virtual users experienced. In other words, if it can be shown that 90 percent of the virtual users fall within a certain response time in a test, then that response time can be assumed to be a reliable predictor of what virtual users will experience. We want to be sure that the 90th percentile time is close to the average time, which suggests that most of the iterations are similar and that outliers are few.

Figure 16. OASB O2C online workload average response time comparison


Figure 17. OASB O2C online workload 90th percentile response time comparison

Table 14 describes each profile used in Figure 16 and Figure 17.

Table 14. OASB O2C online Profiles

Abbreviation Definition

ARCS AR_Costumer_Summary

ARIMI AR_Invoice_Manual_Insert

OMIO OM_Insert_Order

OMOSR OM_Order_Summary_Report

OMPR OM_Pick_Release

OMSC OM_Ship_Confirm

Note For a detailed description of the profiles in the graphs, see the Supporting information section.

As shown in Figure 16 and Figure 17, the provisioning operations had little impact on the performance of the production environment. Figure 16 shows the average response time that all the virtual users experienced when running the O2C profiles. Figure 16 also shows the same result for the 90th percentile response time, which means that for the virtual users running these profiles, 90 percent of them only experienced minimal increase in response time during the provisioning, compared with the baseline. Examine profile OM_Insert_Order as an example: the average response time of all the virtual users running this profile increased 2.85 percent (from 2.068 seconds to 2.127 seconds), and the response time of 90 percent virtual user increased 6.8 percent (from 2.766 seconds to 2.954 seconds), compared with the baseline. We can conclude that when comparing these figures with the baseline, the performance impact on the production environment caused by the provisioning operations was negligible.

O2C batch workload

Figure 18 shows the elapsed time of each batch business process between the baseline testing and cloning testing.


36

Figure 18. OASB O2C batch performance comparison


Table 15 describes each business process used in Figure 18.

Table 15. O2C batch business processes

Abbreviation Definition

HVOP High Volume Order Processing

PR Pick Release

ITS Interface Trip Stop

IWT Inventory work time

AI Auto Invoice

RR Revenue Recognition

AC Accounting

Note For a detailed description of the processes in the graph, see the Supporting

information section.

As shown in Figure 18 , we observed a slight increase in elapsed time for each of the business process steps of the O2C batch workload. The performance differences were within 10 percent when compared with the baseline. We can conclude that for the batch workload, the performance impact on the production environment caused by the provisioning operations was minimal.


38

Conclusion

Reducing the time, effort, and cost associated with deploying, scaling out and provisioning Oracle E-Business Suite test/dev/patch/ environments during the application lifecycle is critical for organizations that rely on Oracle E-Business Suite environments for their business.

This solution deploys the EMC OSC Integration Module into an Oracle VM virtualized E-Business Suite system running on the EMC VMAX 40K array, which provides administrators with an easy and efficient way to manage the Oracle E-Business Suite system in an Oracle VM virtualized environment.

With only a few clicks on the Oracle VM Manager console, Oracle E-Business Suite administrators can easily perform many of the involved management tasks required to support an Oracle E-Business Suite system, such as:

• Virtual machine deployment

• Raw physical disks creation

• Raw physical disk cloning

This enables Oracle E-Business Suite administrators to be agile and efficient, because they can now complete tasks that traditionally required other data center teams (such as the storage team). In addition, it gives the Oracle E-Business Suite administrators greater control over their Oracle E-Business Suite environments.

Ranges of tests were completed to illustrate and validate the functionality and performance of this solution to demonstrate several benefits:

• Efficiency of people, process and technology with Oracle E-Business Suite by implementing EMC OSC Integration Module on the Oracle VM servers simplified the management of the EMC VMAX 40k array using the Oracle VM Manager console, which greatly enhances the efficiency of the administrators.

• Performance – Minimal performance impact on the existing production environment during the test/dev environment provisioning tasks.

• Resiliency – A fast and easy method to deploy new Oracle E-Business Suite environments, scale out the existing environment, and provision test/dev environment.

• Agility – Multiple Oracle E-Business Suite test/dev environments provisioning in an efficient and agile way using EMC OSC Integration Module.

We performed a range of tests to validate the functionality and performance of this solution and to demonstrate several benefits.

Summary

Findings


By enabling the EMC Oracle VM Storage Connect Integration Module on the Oracle VM Server, the management of the VMAX 40K array can be accomplished on the Oracle VM Manager console, which greatly enhances the efficiency of the administrator. When combined with other Oracle features (such as virtual machine template), managing the Oracle E-Business Suite in its application lifecycle is greatly simplified:

• The initial deployment and scaling out of Oracle E-Business Suite environment is made simple.

• Nondisruptive fast test/dev Oracle E-Business Suite environment provisioning has minimal performance impact on the Oracle E-Business Suite production environment.

• Centralizing the Oracle E-Business Suite deployments into the same infrastructure provides better hardware resources utilization and reduces the software license cost.


40

References The following documents, located on the EMC online support website or Powerlink, provide additional and relevant information. Access to these documents depends on your login credentials. If you do not have access to a document, contact your EMC representative.

For additional information, see the EMC white papers listed below.

• Fully virtualized Oracle EBS environment by Oracle VM

• EMCSMI-S Provider Version 4.5 Release Notes

For additional information, see the EMC product documents listed below.

• EMC Oracle Storage Connect Integration Module Release Notes

• EMC Symmetrix VMAX Virtual Provisioning Space Reclamation and Application Considerations—Applied Technology

For additional information, see the documents listed below.

• Oracle VM User’s Guide for release 3.1.1

• Oracle VM Getting Started Guide for release 3.1.1

• My Oracle Support Knowledge Document 465915.1: Using Oracle VM with Oracle E-Business Suite Release 11i or Release 12

• My Oracle Support Knowledge Document 761566.1: Oracle E-Business Suite Installation and Upgrade Notes Release 12(12.1.1) for Linux x86-64

• My Oracle Support Knowledge Document 823587.1: Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12

• My Oracle Support Knowledge Document 384248.1: Sharing The Application Tier File System in Oracle E-Business Suite Release 12

• Certified Software on Oracle VM [ID 464754.1]

• My Oracle Support Knowledge Document 783044.1: Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12.

• Oracle Real Application Clusters Installation Guide 11g Release 2 (11.2) for Linux

• Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Linux

• Cloning Oracle Applications Release 12 with Rapid Clone [ID 406982.1]

• Database Initialization Parameters for Oracle Applications Release 12 [ID 396009.1]

• Guidelines to setup the Java Virtual Machine in Apps E-business Suite 11i and Release 12 [ID 362851.1]

• Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone [ID 559518.1]

White papers

Product documentation

Other documentation

https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(from=BOOKMARK&bmDocTitle=Cloning%20Oracle%20Applications%20Release%2012%20with%20Rapid%20Clone&viewingMode=1143&bmDocType=BULLETIN&bmDocID=406982.1&bmDocDsrc=K�

https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(filterSource=KB&startIndex=1&cmd=getAllNodes&requestedFacets=587,5&facetIdClicked=&clickstreamSource=Bookmark&back=true&userQuery=396009.1&enterprise=true&defa�

https://support.oracle.com/CSP/ui/flash.html#tab=KBHome(page=KBHome&id=()),(page=KBNavigator&id=(filterSource=KB&startIndex=1&cmd=getAllNodes&requestedFacets=587,5&facetIdClicked=&clickstreamSource=Bookmark&back=true&userQuery=396009.1&enterprise=true&defa�


• http://www.oracle.com/us/technologies/virtualization/storage-connect/overview/index.html

• http://www.oracle.com/us/solutions/benchmark/apps-benchmark/index.html

http://www.oracle.com/us/technologies/virtualization/storage-connect/overview/index.html�

http://www.oracle.com/us/technologies/virtualization/storage-connect/overview/index.html�


42

Supporting information

The following sections describe the Oracle Applications Standard Benchmark (OASB). For a detailed workload descriptions, visit Oracle website: http://www.oracle.com/us/solutions/benchmark/apps-benchmark/description-166952.html#R12.

OM_Insert_Order (OMIO)

Business process Description

OM_Insert_Order (OMIO) The user navigates to the “Orders” page, enters customer information and creates a 5-line order. Finally, the user clicks on “Book Order” to enter the completed order. The response time is to ‘save’ the entry.

OM_Order_Pick_Release (OMPR)


OM_Order Pick_Release (OMPR)

The user navigates to the “Shipping/Release Sales Order” page and enters the order number and clicks on “Execute Now.” Finally, the user clicks on “OK” to acknowledge the “Pick Release Only” has completed. The response time is to ‘save’ the entry

OM_Ship_Confirm (OMSC)


OM_Ship_Confirm(OMSC) The user navigates to the “Shipping/Transactions” page and enters “From Order Number” and “To Order Number” before clicking on “Find”. Finally, the user clicks through the confirmation steps and then clicks on “OK” to acknowledge that “Ship Confirm” has completed. The response time is to ‘save’ the entry.

AR_Invoice_Manual_Insert (ARIMI)


AR_Invoice_Manual_Insert (ARIMI)

The user navigates to the “Transactions/Transactions” page and enters Source, Reference Number, and Line Item information. After entering 5 items, the user saves the form. The response time is to ‘save’ the entry.

Introduction

OASB O2C online workload

http://www.oracle.com/us/solutions/benchmark/apps-benchmark/description-166952.html#R12�

http://www.oracle.com/us/solutions/benchmark/apps-benchmark/description-166952.html#R12�


OM_Order_Summary_Report (OMOSR)


OM_Order Summary_Report (OMOSR)

The user navigates to the “Report, Requests/Run Reports” page, submits a New Request “Single Request”, and finds the program with name “Order/Invoice Summary Report”. In the parameter form, enter the parameters “Order Number From” and “Order Number To”, and click through the confirmation steps. Finally, click on “Yes” to submit another request.

AR_Customer_Summary (ARCS)


AR_Customer_Summary (ARCS)

The user selects responsibility “Receivables, Vision Operations (USA)” and navigates to the “Customers" → "Standard” page, enters the customer number, clicks on FIND, clicks on OK on the next form “Organizations”, and clicks on OPEN on the next form “Customer Standard”, and clicks on OPEN on the next form “Customers Address”, then come back to the “Customer Address” form, click on “Ship To” row, clicks on OPEN. Finally, close all forms.

Business process Function

High Volume Order Processing (HVOP)

The HVOP program processes orders by reading the rows from the Order Management Interface tables and converting the interface records into permanent order headers and their respective order lines. The orders are then booked and advanced to the shipping state.

Pick Release (and Ship Confirm)

Pick Release finds and releases the eligible delivery lines that meet the release criteria, and creates move orders. The process of transacting move orders creates a reservation and determines the inventory source sub-inventory.

Ship Confirm is the process of confirming that items have shipped. When a delivery is ship-confirmed, Shipping Execution confirms that the delivery lines associated with the delivery have shipped.

O2C batch workload


44

Business process Function

Interface Trip Stop The deliveries created in the previous step are then assigned to trips, which may involve multiple stops depending upon the shipping addresses of the deliveries. SRS has been modified to accept Organization code as a parameter and process the trip stops for the specified organization. Interface Trip Stop - SRS has also been enhanced to spawn multiple child processes to process trip stops in parallel. The parameter Stops per Batch is used to specify the number of stops to be processed by each thread of the Interface Trip Stop - SRS. Interface Trip Stop - SRS has also been enhanced to defer the Inventory Interface processes. In the E-Business Suite kit, this profile is set to Yes so that the Inventory Interface transactions are processed in the background by the Inventory transaction manager.

INV Material The material transaction manager is configured to execute material transaction by periodic concurrent request submissions and by direct submission of multiple transaction managers via the benchmark SQL script.

Auto Invoice The Auto-Invoice process is used to import invoices, credit memos, debit memos, and on–account credits. ‘Receivables’ ensures that the data imported is accurate and valid.

Revenue Recognition

Revenue Recognition program generates the revenue distribution records for the invoices and credit memos that use Invoicing and Accounting Rules. Accounting rules were assigned to recognize revenue over a 12-month accounting period. The Revenue Recognition program will create distribution records for the invoices and credit memos that are created in Receivables and imported using Auto-Invoice.

Accounting Transfer to General Ledger & Journal Import:

The General Ledger Interface program transfers Receivables transaction accounting distributions to the general ledger interface table (GL_INTERFACE) and creates either detailed or summarized journal batches. “Receivables” creates un-posted journal entries in general ledger and executes Journal Import from Oracle General Ledger. It posts journal batches in Oracle General Ledger to update account balances.

General Ledger Auto-post:

This posts journal batches to update the account balances of the detail and summary accounts. It can post actual budget or encumbrance journal batches.

h11209: emc oracle storage connect integration module ... · pdf filethis white paper...

Documents