0% found this document useful (0 votes)
97 views29 pages

Configuring JDeveloper

The document discusses configuring JDeveloper for OAF. It describes installing JDeveloper, setting up the required version based on the E-Business Suite version, and configuring default project properties and a database connection. It also reviews naming conventions for OAF components and provides steps for creating a sample page, including generating source code.

Uploaded by

Mustafa Taha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
97 views29 pages

Configuring JDeveloper

The document discusses configuring JDeveloper for OAF. It describes installing JDeveloper, setting up the required version based on the E-Business Suite version, and configuring default project properties and a database connection. It also reviews naming conventions for OAF components and provides steps for creating a sample page, including generating source code.

Uploaded by

Mustafa Taha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 29

Section-2

Configuring JDeveloper For


OAF

1
Outline

 JDeveloper Version
 Jdeveloper Installation and Folder Structure
 Steps to configure Jdeveloper
 Running Sample HelloWorld

2
JDeveloper Version

 JDeveloper is the IDE for the below


frameworks
 OAF, ADF, SOA, BPM etc many more
 What differs in each version is the
plugin used in JDeveloper
 JDeveloper – which is required for
OAF is available only from
support.oracle.com website
 OA Framework - How to Find the
Correct Version of JDeveloper for
OA Extensions to Use with E-
Business Suite 11i or Release 12.x
(Doc ID 416708.1)
3
JDeveloper Version(Cont)

 Identify the OA Framework version in your instance by setting the


FND: Diagnostics / FND_DIAGNOSTICS profile option to activate
Diagnostics
 Select the "About This Page" link from any OA Framework page.
 Select the "Technology Components" tab

4
JDeveloper Version(Cont)

OAF Version(E-Business Required Oracle


Suite Version) JDeveloper 10g Patch(es)
12.2.7 Patch 28163665
12.2.6 Patch 24611686
12.2.5 Patch 22064122
12.2.4 Patch 19170592
12.2.3 Patch 17888411
12.2 Patch 17513160
12.1.3 Patch 9879989

5
JDeveloper Version(Cont)

6
JDeveloper Installation

2 Create shortcut to the file jdevW.exe

7
JDeveloper Configuration

8
JDeveloper Configuration(Cont)

1 3

2 9
JDeveloper Configuration(Cont)

 Setup Default Project Properties

10
Create DB Connection(APPS Schema)

11
12
Steps to Create
Page

13
14
15
16
17
18
19
20
Validate the generated files

Source Code

Compiled Code

21
Application Credentials

22
Steps to Configure

 Jdevw.exe (ShortCut)
 Default Project Properties
 APPS (Database Schema) Credentials
 DBC File

23
Naming Conventions

 OAWorkspace
 Top Level Hierarchy to start any page
 File Extension is : .jws
 Only for development purpose – not used while deploying
 OAProject
 Second Level Hierarchy to start any page
 File extension is : .jpr
 Only for development purpose – not used while deploying
 *.jpx file – will be used during VO Extensions (Substitution)

24
Naming Conventions

 Package
 Java Package (Folder Structure)
 All small letters (Preferred and followed even by Oracle Standard
Pages)
 Package Structure Rule (Mandatory)
 For OAF Pages/Regions/Controllers
 <client_name>.oracle.apps.<valid_top_name>.webui
 sreeram.oracle.apps.fnd.webui
 No Validation done on the client name
 Validation will be done on the valid top name – OAF Page will not work if
the application top name mentioned is wrong

25
(sreeram – is client name , FND – Valid Top Name)
Naming Conventions(Cont)

 For ApplicationModule/ViewObject
 <client_name>.oracle.apps.<valid_top_name>.server
 sreeram.oracle.apps.fnd.server
 For EntityObject
 <client_name>.oracle.apps.<valid_top_name>.schema.server
 sreeram.oracle.apps.fnd.schema.server
 For ListOfValues(LOV)
 <client_name>.oracle.apps.<valid_top_name>.lov.server
 sreeram.oracle.apps.fnd.lov.server
 For PopList(DropDown)
 <client_name>.oracle.apps.<valid_top_name>.poplist.server
 sreeram.oracle.apps.fnd.poplist.server
26

(sreeram – is client name , FND – Valid Top Name)


Naming Conventions(Cont)

Component Rule Sample Name FilesGenerated


ApplicationModule <BusinessService>AM EmployeeServicesAM EmployeeServicesAM.xml
EmployeeServicesAMImpl.java
EntityObject <DBObject>EO EmployeeEO EmployeeEO.xml
EmployeeEOImpl.java
ViewObject <BusinessPurpose>VO EmployeeDetailsVO EmployeeDetailsVO.xml
EmployeeDetailsVOImpl.java
EmployeeDetailsVORowImpl.java
Pages <BusinessPurpose>PG EmployeeUpdatePG EmployeeUpdatePG.xml
Regions <BusinessPurpose>RG EmployeeDeptRN EmployeeDeptRN.xml
Controller <BusinessPurpose>CO EmployeeUpdateCO EmployeeUpdateCO.java

27
Optional Configuration
Tools → Preferences

28
Review

 JDeveloper Configuration
 Naming Convention
 Sample Page

29

You might also like