Wednesday, April 28, 2010

USR file is cached somewhere in Portal Admin Console

If you target server is in production mode, it does not apply changes in the datasync file. You can easily update this by deleting the Datasync records in the portal database prior to deploying the new ear containing the changes to the .usr files.




Here is the SQL I run when ever I need to update user properties:



delete from DATA_SYNC_ITEM

where APPLICATION_ID = (

Select dsa.APPLICATION_ID from DATA_SYNC_APPLICATION dsa

where dsa.application_name ='+EAR_APP_NAME+')



Once you run the SQL above, deploy the new ear and your new properties will now appear in the Portal Admin Tool. Propagation is not worth the trouble to update user properties as it is SLOWER than MOLASSES.
 
you can go through the below links :
 
http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/prodOps/propToolAdvanced.html
 
http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/prodOps/datasync.html

2 comments:

  1. Hi, I am new to WLP. Please assist me how can I create content in runtime, using portlet and also changed content will be seen by the user.

    ReplyDelete