Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 62 Insurance
- 536.1K On-Premises Infrastructure
- 138.2K Analytics Software
- 38.6K Application Development Software
- 5.7K Cloud Platform
- 109.4K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.2K Integration
- 41.6K Security Software
Pages Access Setting in runtime back to the default value after redeployment

Hi,
I'm developing Webcenter Portal - Framework Application using Oracle ADF.
At first, we already assign custom role/user to Pages Access in runtime Webcenter Portal Administration Console.
Then, after redeployment the Pages Access setting back to the default value.
Is there any way to make the configuration stay after redeployment?
Thanks,
ricky
Answers
-
Have you tried to preserve runtime customizations?
See Understanding WebCenter Portal Applications - 11g Release 1 (11.1.1.5.0)
-
hi Jiri,
I have tried that method, but it didn't work.
Actually the custom role that I assign to Page Access(page: User Guide) in runtime is 'ADM_PPO',
but after redeployment the role for User Guide page is changed to user admin in webcenterportal ('66666').
so it is not really setting back to the default value but changed to admin.
66666 is a user that has administrator role in our Portal.
thanks,
ricky
-
Hi.
When packaging the .EAR file you can select if bring or not the application policies and the credentials to be override.
Go to Application Properties -> Deployment. In Security Deployment Options you can uncheck the options to prevent losing the changes after a re-deployment.
Regards.
-
Hi Daniel,
The problem is solved after i unchecked the Application Security in Security Deployment Options.
But I realized something,
1. It doesn't work if I do the redeployment after I delete the existing/previous deployment on the weblogic.
go to Weblogic Console - Deployment - delete the previous deployment, then do redeployment from JDev
2. It works if I do the redeployment without deleting the existing/previous deployment
Thanks anyway for the answer
regards,
ricky