The views expressed on this blog are my own and do not necessarily reflect the views of any Organisations owning these products.I keep on doing R & D with different products in and around Middle ware stack and these posts are result of that.Most of the post are result of my own experiments or ideas taken from other blogs .If in any case You feel content is not right you can comment to remove that post. This blog uses the default features,cookies of blogspot.com
Monday, May 26, 2014
Preserving Customization across multiple application run
In the previous exercise we created a page in our portal.
Lets close the page and then redeploy the page again to the integrated weblogic server.
This time now you will find that the HelloWorld page that you have created is not appearing in the page.
The reason for the same is that we have made the changes at run time and those changes were not preserved in the design time environment of Jdeveloper.
The run time portal by default uses MDS to store the changes and this needs to be made sync with the design time environment so that the changes made in the portal can be preserved.
As a best practice it is always recommended to do the changes in the Design time rather than at run time.
But for this exercise we will see how we can preserve the changes made at run time so that it can persist across multiple application run.
In order to persist the changes.
Go to Application and select Application properties
Expand the run and select MDS in the left hand side.
NOw in the right hand side select the option "Preserver customizations across multiple runs"
YOu can also observer the default location for MDS where all the run time changes are getting stored.
Save all the changes and now all the new application that will be run will have the changes.
However for the development purpose it is always better to do the changes in design time hence from next exercise onwards we will make the changes in Jdeveloper and we will also not use the "Preserver customizations across application runs" for next exercises.
No comments:
Post a Comment