You are on page 1of 24

OAF Personalization

Development & Migration

- Sridhar
sridhar.ittrainer@gmail.com

How to Enable Personalization link


for OAF Pages?
Set the value for following profiles
FND: Personalization Region
Link Enabled to Yes (Minimal will
also do but better to set Yes so that
you get personalization links for all
the regions)
Personalize Self-Service Defn
to Yes
Disable Self-Service Personal to
No

OAF Personalization
Hierarchy
Personalization's at lower levels override
personalizations at higher levels
Values inherit the definition from the level
immediately above unless changed
Order of precedence from highest to
lowest:
Function ( Highest)
Site
Operating Unit
Responsibility (Lowest)

Personalize the page


Task : We will personalize the page to render the
attach image column to false.

Click on Personalize Page Link

Click on Personalize Link

Set the Rendered Value to false

Click on Apply

Observe that : Shown Property is Null Now

Page After Personalization

OAF Personalization
Migration
Set profile option FND:
Personalization Document Root
Path. The value of this profile option
will be the directory name
onmiddle-tier.
Ensure that this directory exists on
mid-tier machine of the destination
environment
example:

Source Environment

Destination Environment

Login to Functional
Administrator Responsibility

Set profile option FND:


Personalization Document Root
Path. The value of this profile
option will be the directory name
onmid-tier
FTP the xxPersonalizations.tar to
the directory specific in above
profile option

Navigate to tab
Personalization

Login to Functional Administrator


Responsibility

Click on Import/Export

navigate to tab Personalization

Search the desired


personalizations for the
application name

Click on Import/Export

Extract the personalilzations

Select and Import the


personalizations that have been
imported

Download the
Personalization
Functional Administrator
Personalization
Search the application which are
personalized and to be migrated to
other instance.

Personalization are exported to the


below directory

Personalization Content in the XML


file

JDR_UTILS
jdr_utils.listdocuments('/oracle/apps/per',TRUE);
jdr_utils.listcustomizations
(p_document
=>'/oracle/apps/per/irc/candidateSelfService/webui/RegCreateAccountPG');
jdr_utils.printdocument
(p_document
=>'/oracle/apps/per/irc/candidateSelfService/server/customizations/site/0/
VisitorAM');
jdr_utils.deletedocument(p_document
=>'/oracle/apps/per/irc/candidateSelfService/server/customizations/site/0/
VisitorAM');

Viewing the Personalization using :


JDR_UTILS

JDR Tables

Table

Details

JDR_PATHS

Stores document paths, packages and there parent


child relationship.
Primary Key: PATH_DOCID

JDR_COMPONENTS

Stores components on documents and OA


Framework pages.
Primary Key: COMP_DOCID, COMP_SEQ

JDR_ATTRIBUTES

Stores attribute/properties of components on


documents and OA Framework pages.
Primary Key: ATT_COMP_DOCID,
ATT_COMP_SEQ, ATT_SEQ

JDR_ATTRIBUTES_TRANS

Stores translated attribute values of document


components or OA framework pages.
Primary Key: ATL_COMP_DOCID, ATL_LANG,
ATL_COMP_REF, ATL_NAME

Query1:
select distinct path_type from JDR_PATHS;
/
Result:
DOCUMENT (for pages and regions)
PACKAGE (for packages/directories path)
Query2:
select * from JDR_PATHS where path_name = 'HelloWorldPG' ;
/
-- Get familiar with the table structure,path_typewill be 'DOCUMENT' for this record.
Query3:
select * from JDR_PATHS where path_docid = <path_owner_docid from query2>;
/
-- This record will point to the parent package/directory.
Query4:
select *
from JDR_COMPONENTS
where comp_docid = <path_doc_id>;
/
-- This will query components of the DOCUMENT. There are no records for a PACKAGE type.
Query5:
select * from JDR_ATTRIBUTES
where att_comp_docid = <path_doc_id>
and att_comp_seq = <sequence id of component whose properties you wish to check>;
/