Oracle Application R12 Training Course

Course objectives:
We aim to cover the following topics about EBS:
I. II. III. IV. V. VI. VII. VIII. IX. X. Overview Installation Architecture Configuration Maintenance Patching and upgrade Cloning The Security model Function Security Profile Options XI. Requests XII. Request management model

I. Oracle Applications Overview

Oracle E-Business Suite

An integrated suite of applications for e-business
Applications Technology Financials HRMS CRM Supply Chain Manufacturing Public Sector

Projects

Stored in an Oracle Database and a File System

Business Data Product

Files

Oracle Applications
Oracle Applications consists of
A file system containing:
Forms Reports Concurrent programs Programs and scripts HTML and Java

An Oracle database containing:

Data objects Code objects

Product Families
Intelligence

Marketing & Sales

Manufacturing

Service

Financials

Human Resources

Learning Management

Public Sector/University

Example Standard Product Identifiers

ID
0 101 222 401

Abbreviation
FND GL AR INV

Full Name
Application Object Library General Ledger Receivables Inventory

HTML Interface

Forms Interface

Concurrent Processing
Concurrent programs:
Typically report on, and update, large volumes of data Are usually data-intensive, long-running tasks Run on the Concurrent Processing server Can run simultaneously with online operations Multiple concurrent programs can run at the same time

II. Installation

Installation phases:
Pre-installation requisites Installation
Installation types

Post-installation tasks

Rapid Install
The Rapid Install utility:
Installs and configures all the components needed for your Oracle Applications system Automates most of the steps required for installing Oracle Applications Release 12 Simplifies both standard and advanced installations Minimizes installation time Allows you to select languages and corresponding character sets Eliminates the possibility of certification issues

Rapid Install
Rapid Install
Database Applications Technology Stack File System

Oracle Application Server 10.1.2 ORACLE_HOME Oracle Application Server 10.1.3 ORACLE_HOME

Technology Stack Components

During the installation process, Rapid Install installs and configures the following technology stack components:
Oracle Database 11g Release 1 (10.1.0) Oracle Application Server 10.1.2 (provides Forms services via Oracle Developer 10g) Oracle Application Server 10.1.3 (provides Web services)

Applications Technology Stack for Release 12

Oracle Applications
Oracle Applications Products

Applications Technology Stack

Oracle Developer 10g
Oracle Application Server 10g

Database Server
Oracle 11g Release 1

Caution!
All of our actions and works have to be guided and documented always return to official Oracle Document

Performing installation phase one:

I- Pre-requisites Platforms: (OS and Architecture) Software: (programs and utilities) Hardware: (CPU, Memory, Spaces) OS users and groups.

Release 12 Platforms
Release 12 is supported on:
Sun Solaris (SPARC) Linux (32-bit and 64-bit) Microsoft Windows HP-UX (PA-RISC) HP-UX (Itanium) IBM AIX 5L

The Oracle Applications Installation Update Notes list platform-specific software requirements
These notes are available on OracleMetaLink See notes page of this slide for the references

Software Requirements
Release Maintenance Tools
Solaris: ar, cc, ld, make, X Display Server Linux: ar, gcc, g++, ld, ksh, make, X Display Server Windows: Microsoft C++, MKS Toolkit, GNU make
See notes page for further details

HP-UX (PA-RISC): ar, cc, aCC, make, X Display Server HP-UX (Itanium): ar, cc, aCC, make, X Display Server IBM AIX 5L: ar, ld, linkx1C, make, X Display Server

The Java Development Kit (JDK) is included with Release 12

With 11i, it had to be installed separately (on most platforms)

CPU Requirements
CPU requirements for running Oracle Applications depend on the:
Number of concurrent users and their usage profiles Number of concurrent manager processes and the types of jobs that they are running Load for activities other than Oracle Applications Size of the database Desired response time

Memory Requirements
To calculate memory requirements for the database machine, consider:
Oracle database overhead Size of system global area (SGA) Number of concurrent users Other software on the machine (not recommended)

Disk Space Requirements

Consider disk space requirements for:
Stage area Language files Applications log and output files Temporary directories and files Updates and patches Other files

Create Operating System Accounts

Single-user installations Multi-user installations

Set Up Stage Directory

Running Rapid Install from a stage area:
Shortens installation time Avoids the need for user access to the CD/DVD drive during the installation

To create the stage area directory:

1. 2. 3. 4. 5. 6. 7. 8. 9. Log in as a user with enough privileges to mount DVDs and write to the chosen stage area Insert the Start Here disk in the DVD-ROM drive Mount the DVD (conditional, depending on platform) Confirm perl 5.0053 or higher is installed and available On UNIX, set the DISPLAY environment variable Run the adautostg.pl script Set up the stage area directory by responding to prompts Indicate the components to be staged Insert the Rapid Install DVDs as prompted

Set Up Stage Directory

Performing installation phase two:

Start Rapid Install from the Stage Area
Once the stage directory has been created, you can start Rapid Install:
UNIX example:
$ cd /u01/Stage12/startCD/Disk1/rapidwiz $ ./rapidwiz

Windows example:
F:\>cd Stage12\startCD\Disk1\rapidwiz F:\Stage12\startCD\Disk1\rapidwiz> rapidwiz.cmd

Standard Installation Steps

Running the Rapid Install Wizard
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Start the Rapid Install Wizard Select a Wizard Operation Oracle Configuration Manager Configuration Choice Global System Settings Database Node Configuration Database Directory Select Licensing Type License Additional Products License Products

Standard Installation Steps (Cont)

Running the Rapid Install Wizard (cont.)
Step 11 Select Country-Specific Functionality Step 12 Select Internationalization Settings Step 13 Primary Applications Node Configuration Step 14 Primary Applications Node Services Step 15 Primary Applications Node Directories Step 16 Review Node Information Step 17 Additional Applications Node Step 18 Shared Applications Node Step 19 Review Additional Applications Nodes Step 20 Review Pre-Install Tests

Standard Installation Steps(Cont)

Running the Rapid Install Wizard (cont.)
Step 21 Review Setup Portion Step 22 Start the Installation Step 23 Monitor Status Indicators and Prompts Step 24 Review Post-Installation Tests Step 25 Review Components Installed

Express Installation
An Express installation sets up a fully configured single-user/single-machine system with either a fresh database or a Vision Demo database You specify basic configuration parameters, such as database type and name, top-level installation directory, and port increments
The remaining directories and mount points are supplied by Rapid Install using default values

This type of installation contains a default set of core Applications products

It uses the US7ASCII character set (for a fresh database) and the UTF8 character set for a (Vision Demo install)

Express Installation
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Start Rapid Install Wizard Select Express Installation Oracle Configuration Manager Configuration Choices Review Pre-install Tests Perform the Installation

Configuration File
In Release 12, the configuration file is:
Called conf_<SID>.txt (was config.txt in Release 11i) Used where the database has not yet been created Stored in three separate locations:
Database 10g R2 <ORACLE_HOME>/appsutil (retained) $INST_TOP (retained) /tmp/<time stamp> (deleted when installation is complete)

Also employed in multi-node installs:

You can copy the file from one machine to another for Rapid Install to use on the second machine

Rapid Install Log Files

Rapid Install saves the log files associated with the installation. They are located as follows:
Database tier log files are stored in the <APPS_BASE>/db/tech_st/10.2.0/appsutil/ log/<CONTEXT_NAME>/<timestamp>.log directory on the database tier node Application tier log files are store in the <APPS_BASE>/inst/apps/<CONTEXT_NAME>/logs/ <timestamp>.log directory on the application tier node

Performing installation phase three: Required Post-installation Steps

Check Login to Oracle Applications Change Default Passwords Configure Database Initialization Parameters Review Security Practices Update PL/SQL Log and Out Directory Implement Product and Country-Specific Functionality Add NLS language Configure Client Software

III. Architecture IV. Configuration

R12 File System

apps inst

Database Tier File System

db

apps_st

tech_st

data
Oracle 11g database files used by Oracle Applications product files

11.1.0
Oracle Home files for the Oracle 11g Database

Application Tier File System

apps

apps_st

tech_st

appl
Oracle Applications product files (APPL_TOP)

comn
Files common across products (COMMON_TOP)

10.1.2

10.1.3

Oracle Homes for the Applications Technology stack

APPL_TOP Structure
apps apps_st apps APPL_TOP
(Other product directories)

admin
<CONTEXT_NAME>.env

au 12.0.0

fnd 12.0.0

inv
12.0.0

(Other product subdirectories and files) APPS<CONTEXT_NAME>.env Administrative Files Product Files

Product Directories
appl APPL_TOP

admin
<CONTEXT_NAME>.env

au 12.0.0

fnd 12.0.0

inv 12.0.0

APPS<CONTEXT_NAME>.env

Common Components Directory

COMMON_TOP

admin log out

java

_pages

util

webapps oacore oafm

java jre unzip

lib ($AF_JLIB) JAR and zip files

classes ($JAVA_TOP) Expanded classes

html META-inf
WEB-inf

webservices web.xml

Applications Technology Stack Directory

tech_st 10.1.2 10.1.3

bin reports forms

Apache j2ee bin

INST_TOP Directory
/u01 oracle VIS

apps

inst apps

db

<CONTEXT_NAME>

INST_TOP

admin

appl

out

logs

conf_<CONTEXT_NAME>.txt

Environment Files
Rapid Install creates a number of environment files:
Filename
<CONTEXT_NAME>.env <CONTEXT_NAME>.cmd

Location
11.1.0.1 ORACLE_HOME

Environment
Oracle Server Enterprise Edition

<CONTEXT_NAME>.env <CONTEXT_NAME>.cmd
<CONTEXT_NAME>.env <CONTEXT_NAME>.cmd <CONTEXT_NAME>.env <CONTEXT_NAME>.cmd APPS<CONTEXT_NAME>.env APPS<CONTEXT_NAME>.cmd

AS 10.1.2 ORACLE_HOME
AS 10.1.3 ORACLE_HOME

Oracle Tools Technology Stack

Java Technology Stack

APPL_TOP
APPL_TOP

Oracle Applications
Consolidated Environment File

Setting the Environment

1. Log in as applmgr (OS apps tier owner) 2. Run the environment or command file for the current APPL_TOP and database 3. If you have made any changes to the environment, check that they are correctly set 4. Ensure that there is sufficient temporary disk space 5. Shut down all concurrent managers if you plan to relink Oracle Applications product files or modify Oracle Applications database objects

Main Applications Environment File

<CONTEXT_NAME>.env

Product Directories and Subdirectories

Paths to Product Directories

Other Environment Information

Modifying Environment Files

Oracle Applications Release 12 automatically uses (and requires) the AutoConfig utility to manage configuration and environment files Files maintained by AutoConfig have a header stating This file is automatically generated by
AutoConfg. It will be read and overwritten.

You should not edit any of these files manually

Where a modification is required, you should make the change using the Oracle Applications Manager interface to AutoConfig
You then run AutoConfig to recreate the configuration and environment files

Applications Context File

Located in $INST_TOP/appl/admin, the Applications context file is an XML file that is: Used by AutoConfig to configure the application tier By default named <SID>_<hostname>.xml A central repository for details of the application tier, including:
Port numbers for Forms and Web services Product-specific port numbers Information about application tier services

Context file variables are set during installation, and may be modified with Oracle Applications Manager
They should not be modified by editing files manually

Application Tier Server Control Scripts

An application tier server process is started or stopped with a command of the following form: <process script name> [stop | start] Shell scripts (.sh) are used on UNIX, and command files (.cmd) are used on Windows For example, to start the Applications listener on UNIX:
$ adalnctl.sh start

To stop the Applications listener on Windows:

C:\> adalnctl.cmd stop

Application Tier Server Control Scripts

The principal application tier server process control scripts are used to start and stop all relevant server processes:

Script or Command File

adstrtal.sh <APPSuser/APPSpwd> adstrtal.cmd <APPSuser/APPSpwd> adstpall.sh <APPSuser/APPSpwd> adstpall.cmd <APPSuser/APPSpwd>

Function
Starts all application tier server processes Stops all application tier server processes

Database Tier Server Process Scripts

The database tier server process scripts are:
Created by Rapid Install during the installation Regenerated by AutoConfig Located in:
<RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>

Used to start and stop server processes on the database tier

Database Tier Server Process Scripts

Script or Command File
addlnctl.sh start <SID> addlnctl.cmd start <SID> addbctl.sh start <option> addbctl.cmd start <option> addlnctl.sh stop <SID> addlnctl.cmd stop <SID> addbctl.sh stop <option> addbctl.cmd stop <option>

Function
Start database listener process

Start database process

Stop database listener process Stop database process

Database Tier Server Process Scripts

To stop or start the database, enter the following:
<process script name> [stop | start] [option]

For example, to shut down the database: UNIX/Linux:

$ addbctl.sh stop normal

Windows:
C:\> addbctl.cmd stop normal

V. Maintenance

The AD Utilities
AD Utility
AD Administration

Description
Performs maintenance tasks on the Oracle Applications file system and database.

AutoPatch

Applies patches and adds new languages and

products.

AD Controller

Manages parallel workers in AD Administration, and AutoPatch.

The AD Utilities
AD Utility
AD Relink

Description
Relinks Oracle Applications executable programs
with the Oracle server product libraries.

AD Merge Patch

Merges multiple patches into a single, integrated patch.

AD Splicer

Registers off-cycle products.

The AD Utilities
AD Utility
File Character Set

Description
Converts a file from one character set to another.

Converter
AD Configuration Reports standard information about the installed configuration of Oracle Applications. AD File Identification Identifies the version of an Oracle Applications file. AD Job Timing Report Provides timing summary reports for jobs run by parallel workers.

The Web-based Utilities

Utility
AutoConfig

Description
Updates the Applications context with new

system configuration and helps manage the

system configuration files. License Manager Licenses products, country-specific functionalities, or languages.

The Web-based Utilities

Utility
Patch Wizard

Description
Determines patches that have not been applied,
but that should be applied to keep the system current. Downloads and merges patches from OracleMetaLink.

Applied Patches

Stores patch history information and allows you

to query patch and file history information.

Running the AD Utilities

To run an AD utility:
1. Set APPS environment file. 2. Type the utilitys program name 3. Answer the prompts 4. Exit by typing abort at any prompt 5. Restart by typing the utilitys program name again

Log Files
AD Administration records your AD Administration session in a text file you specify. Enter your AD Administration log file name or press [Return] to accept the default name shown in brackets. Filename [adadmin.log] :

Worker Log Files

Worker log files are:
Called adwork<number>.log Written to the APPL_TOP/admin/<SID>/log directory

Restart Files
Restart files:
Are used by an AD utility to continue processing at the point where it stopped Reside in the APPL_TOP/admin/ <SID>/restart directory Contain information about what processing has already been completed, so that the utility can pick up where it left off

Maintenance Mode Introduction

Maintenance Mode is a mode of operation that makes an Oracle Applications system accessible only for AutoPatch sessions Greatly improves performance by minimizing downtime Using OAM, system administrators can schedule downtime and notify users

Maintenance Mode
There is a Change Maintenance Mode menu in AD Administration to enable or disable Maintenance Mode Alternatively, you can use Oracle Applications Manager