OA FRAMEWORK Class NOTES (Some Of the Points Understand After Explanation )

Desk top Applications

1) Should be required environmental support like jinitiator

2)Performance is low

3)look and feel is less

Doesn't have BLAF, As well as not that

much RICH Components

4) Partially API Support

5) Development time high

6) Integration is not that much simple like webservices etc

7) which doesn't follows oops standards (Robust and Secure)

Web Based Applications :

1) which doesn't required any environmental support with in the LAN,WAN

2) Performance high

3) look and feel is high

4) Native API Support

5) Development time less

6) Integration is very simple like web services etc

7) which follows oops standards (Robust and Secure)

 Framework :

---------------

Collection of API's which provides end to end solutions for enterprise applications

Apps version Reports Forms mw

Report Builder 7 Form builder 7 Workflow

11i XML Publisher 3 Jsp 3

Discoverer OAF

Report Builder 3 Form builder 3 Workflow

R12 XML Publisher 7 Jsp 7

Discoverer OAF

OBIEE ADF SOA

FUSION HYPERION ADF SOA

Frameworks From ORACLE

AK

JTF

OAF

ADF

OAF Is
Why oracle Selected Java

J2SE

J2EE -- Web Based App

J2ME
MVC :

MVC Stands for model view controller

Which follows J2EE Guide lines

Main Advantage of the MVC Is :

Which Separates the business logic From presentation Area

It's basically follows loosely coupled and improves

 Maintenance is simple
 Performance
 Reusability because of Loosely Coupled
OAF Related MVC Guide Lines :
OA FRAMEWORK Class NOTES (Some Of the Points Understand After Explanation )
-----------------------------------------

Package :

----------

java.io

java.lib

java.sql

java.util

java.lang

java.math

Standard Page

--------------

oracle.apps.applicationshortname.componentname.webui
oracle.apps.applicationshortname.componentname.server

Custom Page

Generally we need to follow below package Structure for all View and controller related files

thirdpartyidentifier.oracle.apps.applshortname.component.webui

For Example :

Page Name : LeaveDetailsPG

gt146.oracle.apps.per.leavemgmt.webui
Generally we need to follow below package Structure for all Model Components
[thirdpartyidentifier].oracle.apps.applshortname.[component].server

For Example :

Page Name : LeaveDetailsVO

gt146.oracle.apps.per.leavemgmt.server

Rules we need follow for package structure :

1) Package Structure Should be lower case

2) It is Positional based syntax

3) keywords you should not disturb ,

optional places we should not use Keywords

4) dot operator significance is separates the folders.

Important Pkg Naming Structure

[thirdpartyidentifier] -- Follow client naming standard

for example client is goutham technologies(gt)

Application short name :

Generally for which application we are working, then we need to enter respective application
short name

Note :

but application should be available in EBS (FND_APPLICATION)

Component Name :

We need to enter meaningful name against object

For example
OA FRAMEWORK Class NOTES (Some Of the Points Understand After Explanation )
payroll

leaves

appraisal

View Components :

-----------------

As part of MVC -- V Stands for VIEW

View :

1) Final Output the of the class is called it as

View Ex : page

2) View components Saved as XML File, Also stored into MDS(Meta Data Services)

3) Extends UIX(User Interactive XML) Framework.

4) we need follow below package structure for all View Components

thirdpartyidentifier.oracle.apps.applshortname.component.webui

5) View components are

1) page,

2) Region,

3) package file
Page :

1) Using this we can able to

display data which

requested by the user.

2) Naming Standard is PG

3) Page holds no of regions (It's may be internal or External)

4) Default region for any page or top -level component of any OAF Page is "PageLaout"
Region

5) Page definitions are stored into MDS(Meta Data Services)

6) UIX(User Interactive XML) Engine will take care of to Generate XML File

7) Saved as XML file.

Region :

1) Region holds no of items or sub regions

2) Naming Standard RN or RG

3) Which follows java beans hierarchy

4) Which are in the Same node called it as siblings,and inside of the node called it

as childs. 5) Regions are 2 types

Internal Regions :

Its

specific to page

External Regions

:

We can use this region into any page and We can achieve Reusability
Concept.

Best Example is List of Values

6) Default region the OAF Page is page layout Region

Package File :

1) Generally Used to set the properties to particular beans

2) we can apply this property set to any bean

For Example

Item - id ,prompt, max length,, etc

we can improve Using package files

a) Reusability

b) Readability

c) bi-lingual support

Model or BC4J or core Components in OAF :

1) Model is used to perform core SQL Operations (DQL,DML,TCL)

2) We required one database connection model project

3) We need to follow below directory structure

[thirdpartyidentifier].oracle.apps.applshortname.[component].server

4) Generally Model components have below file formats

xml and java

Note :Java files always optional

Model Components :

1) View Object and View lInks :

1) a) Generally select statement called it as View Object

b) As part of java terminology, It is called a row set

2) Naming Standard is VO

3) Files generally we are using respective to VO Are

a) VO.xml, b) VOImpl.java, c) VORowImpl.java

4) we have 2 Types of VO's in OAF

1) Read Only VO :

a) we can build Without entity object

b) We can't perform DML Operations Using this VO

c) We can create programmatically.

2) Updatable VO :

a) we can't build Without entiy object/s

b) We can perform DML Operations Using this VO

c) We can't create programmatically.

5) Generally Terminology point of view in OAF Is,

Query called : VO,

Query Columns called : Attributes

7) Each Attribute Capable to read the Data dictionary

8) Parent Class for All VO's OAViewObjectImpl

For Example :

VO Name : DeptVO, EmpVO , SupplierSearchVO

View Links

1) These are Used to join between 2 VO' more than 2 VO'

2) Naming standard is VL

For Example :

DeptVO, Emp VO

View Link Name : DeptToEmpVL

Entity Object and Associations :

1) a) Generally table or view or synonym or materialized view called It as Entity object in OAF

b) As part of java a single row

2) Using this we can perform DML Operations

2) Naming Standard is EO

3) Files generally we are using respective to EO Are

EO.xml, EOImpl.java

4) We have 2 types of EO's in OAF

1) Entity Object

2) PLSQL Entity Object

5) EO have below life cycle Framework Methods

a) Accessors

b) create

c) doDML

d) Validate Entity

e) remove

6) Parent Class for All EO's iS OAEntityImpl

7) Always Entity Object holds 1-1 Relationship

For Example :

EO Name :

DeptEO, EmpEO
Associations :

1) Associations are used to relationship between 2 EO's or more than 2 EO's

2) Generic Use case is on cascade delete

3) Naming standard is Assc

For Example :

DeptEO, EmpEO

Assc Name : DeptToEmpAssoc

Application Module

1) Which holds the business logic and which maintains relationship between all our bc4j components

2) holds the instances of VO's and View Links and Application Module's

3) It will perform Connection Management, TCL Operations

4) AM also divided, as part of usage in the OAF Is

1) Root AM

2) nested AM

5) Application Module is Mandatory component in the OAF For Any page

6) Naming Standard is AM

7) Files generally we are using respective to AM Are

Files are AM.xml

AMImpl.java

8) Parent Class for All AM's iS OAApplicationModuleImpl

9) We can test and Run the Instances Using Business Components browser
Jdeveloper

1) 4 GL wizard based Development

2) Help system Support

3) Dependent Analysis framework

4) Powerful loggers,debuggers,profilers,watchers etc

5) powerful and Robust & multi threaded contextual linking and seem less integrated editors

6) Inbuilt SQL Developer

Main window's Used in Jdeveloper for OAF Development:

1) Application Navigator :

Design the Application like MVC Component, project, workspace

2) Connection Navigator :

Establish Database

Connection

3) Structure pane :

Arrange the Structure for Page or Region based on requirement

4) property Inspector :

Set the Properties, prompt,id,maximumlength -- etc

5) Code Editor :

To Write business logic (Java

Editor) 6) Log Window

Configuration Steps For OAF To Jdeveloper

1) Identify and download the Required version of jdeveloper respective to EBS

http://oracleapps88.blogspot.in/2011/10/to-find-correct-version-of-jdeveloper.html

2) Extract the zip file

3) Set the DBC File

4) Set the Environmental Variables

Variable Name : JDEV_USER_HOME

Variable Value : Extracted Drive/Extracted Folder/JdevHome/Jdev

5) take the shortcut of jdevw.exe.