Move OA Framework personalizations

How do we move the personalization from one environment to another?

Source Environment	Destination Environment
Set profile option “FND: Personalization Document Root Path”. The value of this profile option will be the directory name on mid-tier Ensure that this directory exists on mid-tier machine of the destination environment
Login to Functional Administrator Responsibility
Navigate to tab “Personalization”
Click on Import/Export
Search the desired personalizations for the application name
Extract the personalilzations
Login to linux/unix mid-tier and cd to directory specified in profile option
Do tar –cvfxxPersonalizations.tar ./*
	Set profile option “FND: Personalization Document Root Path”. The value of this profile option will be the directory name on mid-tier Ensure that this directory exists on mid-tier machine of the destination environment
	FTP the xxPersonalizations.tar to the directory specific in above profile option
	Cd to that directory
	tar –xvf xxPersonalizations.tar *****
	Login to Functional Administrator Responsibility
	Navigate to tab “Personalization”
	Click on Import/Export
	Select and Import the personalizations that have been imported

What are common pitfalls, that one must be careful about? 1. Responsibility level personalizations extracted with RESPONSIBILITY_ID in directory path. 2. Substitutions of BC4J objects are also extracted Lets have a deeper look at these issues Responsibility level personalizations issue Lets assume You have created a new responsibility in development system. Name of responsibility is “XX HRMS Manager” Its responsibility_id in development system is 1032 You have done responsibility level personaliation for OAF Pages, for this resp. Issue:- When you extract the personalizations, the directory path of extracted personalizations will contain the responsibility_id However, the same responsibility when created on TEST SYSTEM might be allocated a responsibility_id of 1088. Hence, you referring to ***** in notes above, you will have to rename the directory from 1032 to 1088. This can be scripted too in Unix. To overcome this issue:-If you wish to perform responsibility level personalizations against a custom responsibility, first create this responsibility on production, and get this cloned to other environments. Alas, such forward planning rarely happens in projects. Blame this on Oracle’ design. They could have easily used RESPONSIBILITY_KEY/APPLICATION_ID in the path, instead of using RESPONSIBILITY_ID. Substitutions of BC4J objects are also extracted You may accidentally export and import the substitutions to BC4J Objects, because substitutions are stored in MDS layer as site level personalizations. In this scenario, you must ensure that relevant extended java classes and xml files are located in $JAVA_TOP of destination environment. SCREENSHOTS   Click on personalization tab   Click on Import/Export   To export personalizations, search for your personalizations and click export to file system   To import personalizations, click on exported personalizations button. This will show the files on file-system. Select the desired personalizations and then click on “Import from File System”