Slide 1

OAF Personalization Development & Migration How to Enable Personalization link for OAF Pages?Set the value for following profilesFND: 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 YesDisable Self-Service Personal to NoOAF Personalization HierarchyPersonalization's at lower levels override personalizations at higher levels Values inherit the definition from the levelimmediately above unless changed Order of precedence from highest to lowest: Function ( Highest) Site Operating Unit Responsibility (Lowest)

Personalize the pageTask : 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 NowPage After Personalization

OAF Personalization MigrationSet 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 EnvironmentDestination EnvironmentLogin to Functional Administrator ResponsibilitySet profile option FND: Personalization Document Root Path. The value of this profile option will be the directory name onmid-tierFTP the xxPersonalizations.tar to the directory specific in above profile optionNavigate to tab PersonalizationLogin to Functional Administrator Responsibility

Click on Import/Exportnavigate to tab PersonalizationSearch the desired personalizations for the application name

Click on Import/ExportExtract the personalilzationsSelect and Import the personalizations that have been importedLogin to linux/unix mid-tier and cd to directory specified in profile option

Do tar cvf xxPersonalizations.tar ./*Download the PersonalizationFunctional 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_UTILSjdr_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

TableDetailsJDR_PATHSStores document paths, packages and there parent child relationship.Primary Key: PATH_DOCIDJDR_COMPONENTSStores components on documents and OA Framework pages.Primary Key: COMP_DOCID, COMP_SEQJDR_ATTRIBUTESStores attribute/properties of components on documents and OA Framework pages.Primary Key: ATT_COMP_DOCID, ATT_COMP_SEQ, ATT_SEQJDR_ATTRIBUTES_TRANSStores 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 = ;/-- This record will point to the parent package/directory.

Query4:select *from JDR_COMPONENTSwhere comp_docid = ;/-- This will query components of the DOCUMENT. There are no records for a PACKAGE type.

Query5:select * from JDR_ATTRIBUTESwhere att_comp_docid = and att_comp_seq = ;/