· Oracle E-Business Suite Release 12: Installation and Cloning Enhancements Robert Farrington Andrew Rist. The following is

<Insert Picture Here>

Oracle E-Business Suite Release 12:Installation and Cloning Enhancements Robert FarringtonAndrew Rist

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remain at the sole discretion of Oracle.


Agenda

• Introduction• Overview of Rapid Install• Release 12 Installation Enhancements• Cloning Enhancements• Q & A

What is Rapid Install?

• Rapid Install is the Oracle Applications installation tool • It is also used in the upgrade process from an earlier release• A specialized additional function is to install the Oracle

technology stack only

• Rapid Install is:• A GUI-based program that runs on UNIX and Windows

platforms• Invoked using the command rapidwiz

Rapid Install Functions

• With Rapid Install, you can perform the following tasks:• Install a new, fully configured Oracle Applications system

• This includes the latest certified Oracle Applications technology stack and all patches, minipacks, and family packs, available at the time of release

• Lay down the file system and configure server processes for an upgraded system

• Install a new database tier or application tier technology stack

How Rapid Install Works

• Rapid Install employs a wizard that guides you through the setup screens needed for a selected task

• On the wizard screens, you enter configuration values• Rapid Install uses these values to determine the configuration

settings for each host in your system • These are saved in the Applications database for later use

• Rapid Install uses this information to run Rapid Clone on each node and set up your system

• If you run Rapid Install again subsequently, you can point it to the stored information• For example, this is useful if performing a distributed install

Behind the Scenes: AutoConfig

• The main configuration engine used by Rapid Install is called AutoConfig

• AutoConfig stores the configuration details for each node in a node-specificcontext file

More About AutoConfig

• AutoConfig also simplifies configuration management• After the initial installation, you can use the

AutoConfig Configuration Editor to update settings• The Editor is part

of Oracle ApplicationsManager

• You then runAutoConfig topopulate the systemconfiguration fileswith new values

Installing New Systems

• Rapid Install automatically supplies values for most of the many parameters your Applications system will need

• You do, however, have a initial choice to make:• You can either supply a number of your own parameters and

carry out a Standard install• You can opt for an Express install and let Rapid Install supply

default values for nearly all the parameters

• A Standard install gives more flexibility, while an Express install is useful if you know that the default settings will suffice or are installing a test system

Database Choice

• Both Standard and Express installs offer the choice of installing either:

• A fresh database (one that is fully configured but contains no transaction data)

• A Vision Demo database (one that contains example transaction data for a fictitious company)

Installation Terminology

• A server is a process or group of processes that provides a particular functionality, often referred to as a service• For example, the HTTP server is a process that listens for

and processes HTTP requests

• A node is a logical grouping of servers, and therefore a software concept• This presentation will refer to the:

• Primary application node (which may be the only one)• Database node, which supports the Oracle database

Installation Terminology

• A tier is a logical grouping of services, potentially spread across more than one physical machine

• The three-tier architecture that comprises an Oracle E-Business Suite installation is made up of the:• Database tier, which supports and manages the Oracle

database• Application tier, which supports and manages the various

Applications components, and is sometimes known as the middle tier

• Desktop tier, which provides the user interface via an add-on component (plug-in) to a standard web browser

Other Rapid Install Functions: Upgrading from Release 11i

• As part of an upgrade from Release 11i to Release 12, you enter configuration parameters in Rapid Install and run it as one of the pre-upgrade tasks• Rapid Install uses the parameters to lay down the file system

and install the new technology stack

• You must also migrate or upgrade an existing database to Oracle 10g Release 2 (10.2.0.2)

• After completing the pre-upgrade tasks, you run AutoPatch to apply patches and run drivers needed

• After completing the database upgrade, you run Rapid Install again to configure and start the servers

Other Rapid Install Functions: Installing a New Technology Stack

• You can upgrade an existing database or application tier node to a new technology stack by running Rapid Install to install only the technology stack components

• As well creating the relevant new ORACLE_HOMEs, this process uses AutoConfig to generate new configuration files for use with the updated technology stack

• Note that you can install a new technology stack without upgrading Applications products• This reduces downtime, while allowing the latest technology

to be used


Agenda


Rapid Install Look and Feel

• Release 12 Rapid Install has the familiar look and feel of previous versions

• The screen flowshave beengreatly simplifiedand streamlined

Online Help Improvements

• The context-sensitive online help has been rewritten for Release 12

Storage of Configuration Details

• In previous releases, configuration details were always stored in a file (config.txt)

• This made transporting the details between machines more problematical

• The configuration file also had to be stored safely in case it was needed on future occasions

• In Release 12, the config.txt file is still used to support:

• Installs where the database has not yet been created• Restarted or scripted installs

Storage of Configuration Details

• In Release 12, the Applications database is used as the primary store for configuration details

• A standarddatabaseconnect stringis used ifloading aconfiguration

Mandatory Use of AutoConfig

• AutoConfig is delivered with, and required by, a new installation of Oracle Applications Release 12

• This was also true for a new installation of Release 11i

• After installation, AutoConfig is used to maintain the various configuration files needed by the Applications system

• The files should not be modified manually, as AutoConfig will overwrite them next time it runs

Shared Application Tier File System: Traditional Model

• A traditional multi-node installation of Release 11i required each application tier to maintain its own file system, consisting of the APPL_TOP file system:

• APPL_TOP• COMMON_TOP• Some related directories

• Plus the Release 11i application tier technology stack file system:

• 8.0.6 ORACLE_HOME• iAS ORACLE_HOME)

Shared Application Tier File System: Release 12 Model

• Release 12 Rapid Install creates a system that shares APPL_TOP and COMMON_TOP, plus the application node technology stack file system

• Result is that all application node files are installed on a single shared disk resource that is mounted on each application node

• This configuration is the default for nodes that are running the same operating system

• Any application node can be used to provide standard services, such a Web serving

• This technology was initially introduced in R11i

Shared Application Tier File System: Release 12 Model Benefits

• Most administration and maintenance tasks need be performed only once, on a single node

• Changes made to the shared file system are immediately accessible on all application nodes

• Reduces overall disk space requirements• Makes adding additional application tier nodes

easier

Application Node Install Screens

• This and the next screen highlight the main Application node install changes in Release 12

• Linux:

11


• This and the previous screen highlight the main Application node install changes in Release 12

• Windows:

11

22

33


• Specify services to be enabled on this application node:


• Specify file system paths on this application node:


• Review details for database node and primary application node:


• Add another application node:

11

Starting the Installation

• Rapid Install then validates the system configuration and allows any problems to be corrected

• You will thenreach thisscreen

• You canstart theinstallationby clickingNext:

Completing the Installation

• After Rapid Install completes, you can connect to Release 12:

Log on to Applications Release 12

• After logging in to Oracle Applications Release 12, you are taken to your home page :


Agenda


Cloning Terminology

• Cloning is the process by which an identical copy of an existing Oracle Applications system is created

• Cloning can create copies of both the database tier and application tier

• A Source system is cloned to a Target system• An Image is a packaged copy of the Source• The Image is stored in a Stage location

• The next slide illustrates basic cloning operation

Cloning Terminology

Stage Apply

text

Source System Target System

Image

Cloning Benefits

• Benefits of cloning include the capability to: • Create a duplicate of the production system to carry out

development or test updates• Create a production system from a successful test

system• Migrate existing system to a new hardware platform• Scale an existing system up or down• Modify topology of an existing system• Enhance system backup and recovery capability by

backing up to and recovering from clone image• Create a standby system in a high availability

environment

What is Rapid Clone?

• Rapid Clone is a system cloning tool available as standard with Oracle Applications

• It can bring a target system to the same patchset and data levels as the source system

• It can produce a target system which is a scaled down, scaled up, or exact copy of the source system

• Rapid Clone is available via:• Command line APIs (adpreclone.pl and adcfgclone.pl)• Application Management Pack for E-Business Suite (Grid

Control plug-in)

• Rapid Clone does not change the data

Common Cloning Scenarios

• Single node source system to single node target system

• Application and database tier on the same source node


• Single node source system to a multi-node target system

• Source system with:• Application and database tier on the same node

• Can be cloned to create a target system where: • Application and database tier are on two separate

nodes


• Multi-node source system to a multi-node target system where both systems have the same number of nodes

• Source system with:• Database tier on one node• Application tier on three other nodes

• Can be cloned to create:• Target system with same configuration


• Multi-node source system to multi-node target system where target system has more nodes than the source system

• Source system with:• Database tier on one node• Application tier on another node

• Can be cloned to create target system where:• Database tier is still on one node• Application tier is now on two nodes

Summary of Cloning Scenarios

Stage

Apply

text

Production System

Interim System

Production Backup

Stage

Scrubbed Image

System Transformations

(Scramble, Purge, Prune, Munge, Alter Credentials)

Transform

Apply

Apply

Copy of Scrubbed

Image

text

Large Test System

Dev System

New Cloning Features

• Application Management Pack for E-Business Suite (Enterprise Manager option) supports:

• Choice of Simple Clone or Advanced Clone:• Simple Clone:

• Creates an exact copy of source system• Advanced Clone gives the flexibility of:

• Specifying advanced options• Extended interview process• Scalability to add or remove machines• Option to add custom steps


• Application Management Pack for E-Business Suite (Enterprise Manager option) also supports:

• Automated Cloning Process• Integration with Grid Control• Step-by-step interview to manage cloning process• Modification of standard cloning process to add custom

actions• Clone Dashboard to monitor status of cloning jobs


• Application Management Pack for E-Business Suite (Grid Control plug-in) supports:

• Automated Cloning Process

• Rapid Clone supports:• Cloning the Release 12 10.1.2/10.1.3 technology stack• Cloning an RAC environment (including Application

Storage Management and Cluster Ready Services)

• Cloning as an overall technology is more closely integrated with E-Business Suite

• Used as part of the installation process• Delivered as an integral feature of a installed system


Agenda



Questions & Answers

For More Information

http://search.oracle.com

orhttp://www.oracle.com/

Documents

· Oracle E-Business Suite Release 12: Installation and Cloning Enhancements Robert Farrington Andrew Rist. The following is