glo training

8/4/2019 Glo Training

1/66

Oracle Application R12

Training Course


2/66

Course objectives:

I. Overview

II. Installation

III. Architecture

IV. ConfigurationV. Maintenance

VI. Patching and upgrade

VII. Cloning

VIII. The Security model

IX. Function Security

X. Profile Options

XI. Requests

XII. Request management

model

We aim to cover the following topics about EBS:


3/66

I. Oracle Applications Overview


4/66

Oracle E-Business SuiteAn integrated suite of applications for e-business

Stored in an Oracle Database and a File System

Applications Technology

Financials

Manufacturing

CRM

HRMS

Supply Chain

Business

Data

Product

Files

Public SectorProjects


5/66

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


6/66

Product Families

Intelligence

Financials

Manufacturing

Learning Management

Human Resources

Marketing & Sales

Service

Public Sector/University


7/66

Example Standard Product Identifiers

ID Abbreviation Full Name

0 FND Application Object Library

101 GL General Ledger

222 AR Receivables

401 INV Inventory


8/66

HTML Interface


9/66

Forms Interface


10/66

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


11/66

II. Installation


12/66

Installation phases:

Pre-installation requisites

Installation

Installation types

Post-installation tasks


13/66

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 correspondingcharacter sets

Eliminates the possibility of certification issues


14/66

Rapid Install

Database File SystemApplications Technology Stack

Rapid Install

Oracle Application Server 10.1.2

ORACLE_HOME

Oracle Application Server 10.1.3ORACLE_HOME


15/66

Technology Stack Components

During the installation process, Rapid Install installs andconfigures 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)


16/66

Applications Technology Stack for

Release 12

Oracle 11g Release 1

Oracle Applications Products

Oracle Applications

Oracle Developer 10g Oracle Application Server 10g

Applications Technology Stack

Database Server


17/66

Caution!

All of our actions and

works have to be guidedand documented always

return to official Oracle

Document


18/66

Performing installation

phase one:

I- Pre-requisites

Platforms: (OS and Architecture)

Software: (programs and utilities) Hardware: (CPU, Memory, Spaces)

OS users and groups.


19/66

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


20/66

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)


21/66

CPU Requirements

CPU requirements for running Oracle Applicationsdepend 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


22/66

Memory Requirements

To calculate memory requirements for the databasemachine, consider: Oracle database overhead

Size of system global area (SGA)

Number of concurrent users Other software on the machine (not recommended)


23/66

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


24/66

Create Operating System Accounts

Single-user installations

Multi-user installations


25/66

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 duringthe installation

To create the stage area directory:1. Log in as a user with enough privileges to mount DVDs and write to the

chosen stage area

2. Insert the Start Here disk in the DVD-ROM drive

3. Mount the DVD (conditional, depending on platform)

4. Confirm perl 5.0053 or higher is installed and available

5. On UNIX, set the DISPLAY environment variable

6. Run the adautostg.pl script7. Set up the stage area directory by responding to prompts8. Indicate the components to be staged9. Insert the Rapid Install DVDs as prompted


26/66

Set Up Stage Directory


27/66

Performing installation

phase two:

Once the stage directory has been created, you can

start Rapid Install: UNIX example:

Windows example:

$ cd /u01/Stage12/startCD/Disk1/rapidwiz

$ ./rapidwiz

F:\>cd Stage12\startCD\Disk1\rapidwiz

F:\Stage12\startCD\Disk1\rapidwiz> rapidwiz.cmd

Start Rapid Install from the Stage Area


28/66

Standard Installation Steps

Running the Rapid Install WizardStep 1 Start the Rapid Install Wizard

Step 2 Select a Wizard Operation

Step 3 Oracle Configuration Manager

Step 4 Configuration ChoiceStep 5 Global System Settings

Step 6 Database Node Configuration

Step 7 Database Directory

Step 8 Select Licensing Type

Step 9 License Additional ProductsStep 10 License Products


29/66

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 ServicesStep 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 NodesStep 20 Review Pre-Install Tests


30/66

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 TestsStep 25 Review Components Installed


31/66

Express Installation

An Express installation sets up a fully configuredsingle-user/single-machine system with either afresh database or a Vision Demo database

You specify basic configuration parameters, such as

database type and name, top-level installationdirectory, 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)


32/66

Express Installation

Step 1 Start Rapid Install Wizard

Step 2 Select Express Installation

Step 3 Oracle Configuration Manager

Step 4 Configuration Choices

Step 5 Review Pre-install Tests Step 6 Perform the Installation


33/66

Configuration File

In Release 12, the configuration file is:

Called conf_.txt (was config.txt in Release 11i)

Used where the database has not yet been created

Stored in three separate locations: Database 10g R2 /appsutil (retained)

$INST_TOP (retained)

/tmp/ (deleted when installation is complete)

Also employed in multi-node installs:

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


34/66

Rapid Install Log Files

Rapid Install saves the log files associated with theinstallation. They are located as follows: Database tier log files are stored in the/db/tech_st/10.2.0/appsutil/

log//.logdirectory on the database tier node

Application tier log files are store in the/inst/apps//logs/.log directory on the application tier node


35/66

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

Performing installationphase three:


36/66

III. ArchitectureIV. Configuration


37/66

R12 File System

apps inst


38/66

Database Tier File System

data 11.1.0

db

tech_stapps_st

Oracle 11g databasefiles used by Oracle

Applications

product files

Oracle Home filesfor the Oracle 11g

Database


39/66

Application Tier File System

apps

apps_st tech_st

appl comn 10.1.2 10.1.3

Oracle Applications

product files(APPL_TOP)

Files common across

products(COMMON_TOP)

Oracle Homes for the Applications

Technology stack


40/66

APPL_TOP Structureapps

apps

12.0.0

fndau

12.0.0

APPS.env

admin

.env

12.0.0

inv

(Other product subdirectories and files)

(Other product directories)

apps_st

APPL_TOP

Administrative Files Product Files


41/66

Product Directories

appl

12.0.0

fndau

12.0.0

inv

12.0.0

admin

APPL_TOP

.env

APPS.env


42/66

Common Components Directory

java util

java unzip

COMMON_TOP

admin _pages webapps

oacore oafmjre

META-infhtml

WEB-inf

web.xml

classes

($JAVA_TOP)

Expanded classes

lib

($AF_JLIB)

JAR and zip files

webservices

log out

A li i T h l S k


43/66

Applications Technology Stack

Directory

10.1.2

bin

forms

Apache

bin

j2ee

10.1.3

reports

tech_st


44/66

INST_TOP Directory

inst

admin

apps

appl logs conf_.txtout

INST_TOP

apps db

VIS

oracle

/u01


45/66

Environment FilesRapid Install creates a number of environment files:

Filename Location Environment

.env.cmd

11.1.0.1

ORACLE_HOMEOracle ServerEnterprise Edition

.env.cmd

AS 10.1.2

ORACLE_HOMEOracle ToolsTechnology Stack

.env.cmd

AS 10.1.3

ORACLE_HOMEJavaTechnology Stack

.env.cmd

APPL_TOP Oracle Applications

APPS.envAPPS.cmd

APPL_TOPConsolidatedEnvironment File


46/66

Setting the Environment

1. Log in as applmgr (OS apps tier owner)

2. Run the environment or command file for the currentAPPL_TOP and database

3. If you have made any changes to the environment,

check that they are correctly set4. Ensure that there is sufficient temporary disk space

5. Shut down all concurrent managers if you plan torelink Oracle Applications product files or modifyOracle Applications database objects


47/66

Main Applications Environment File

.env

Product Directories and

Subdirectories

Paths to Product Directories

Other Environment Information


48/66

Modifying Environment Files

Oracle Applications Release 12 automatically uses(and requires) the AutoConfig utility to manageconfiguration and environment files

Files maintained by AutoConfig have a header

stating This file is automatically generated byAutoConfg. It will be read and overwritten. You should not edit any of these files manually

Where a modification is required, you should makethe change using the Oracle Applications Manager

interface to AutoConfig You then run AutoConfig to recreate the

configuration and environment files


49/66

Applications Context File

Located in $INST_TOP/appl/admin, the Applications context file isan XML file that is:

Used by AutoConfig to configure the application tier

By default named _.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


50/66

Application Tier Server Control Scripts

An application tier server process is started or stoppedwith a command of the following form:

[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:

To stop the Applications listener on Windows:

$ adalnctl.sh start

C:\> adalnctl.cmd stop


51/66

Application Tier Server Control Scripts

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

Script or Command File Function

adstrtal.sh

adstrtal.cmd Starts all application tierserver processes

adstpall.sh

adstpall.cmd Stops all application tierserver processes


52/66

Database Tier Server Process Scripts

The database tier server process scripts are:

Created by Rapid Install during the installation

Regenerated by AutoConfig

Located in:/appsutil/scripts/

Used to start and stop server processes on thedatabase tier


53/66


Stop database process

Stop database listener processaddlnctl.sh stop

addlnctl.cmd stop

Start database processaddbctl.sh start addbctl.cmd start

Start database listener processaddlnctl.sh start

addlnctl.cmd start

FunctionScript or Command File

addbctl.sh stop addbctl.cmd stop


54/66


To stop or start the database, enter thefollowing:

[stop | start] [option]

For example, to shut down the database:

UNIX/Linux:

Windows:

$ addbctl.sh stop normal

C:\> addbctl.cmd stop normal


55/66

V. Maintenance


56/66

The AD Utilities

AD Utility Description

AD Administration Performs maintenance tasks on the Oracle

Applications file system and database.

AutoPatch Applies patches and adds new languages andproducts.

AD Controller Manages parallel workers in AD Administration,

and AutoPatch.


57/66

The AD Utilities


AD Relink Relinks Oracle Applications executable programs

with the Oracle server product libraries.

AD Merge Patch Merges multiple patches into a single, integratedpatch.

AD Splicer Registers off-cycle products.


58/66

The AD Utilities


File Character Set

Converter

Converts a file from one character set to another.

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.


59/66

The Web-based Utilities

Utility Description

AutoConfig Updates the Applications context with new

system configuration and helps manage the

system configuration files.

License Manager Licenses products, country-specific

functionalities, or languages.


60/66

The Web-based Utilities

Utility Description

Patch Wizard 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.


61/66

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


62/66

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] :


63/66

Worker Log Files

Worker log files are: Called adwork.log

Written to the APPL_TOP/admin//log directory


64/66

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/ /restart directory

Contain information about what processing has already beencompleted, so that the utility can pick up where it left off


65/66

Maintenance Mode Introduction

Maintenance Mode is a mode of operation that makesan Oracle Applications system accessible only forAutoPatch sessions

Greatly improves performance by minimizing downtime

Using OAM, system administrators can scheduledowntime and notify users


66/66

Maintenance Mode

There is a Change Maintenance Mode menu in ADAdministration to enable or disable Maintenance Mode

Alternatively, you can use Oracle Applications Manager

glo training

Documents