I first created a sample application with simple authentication, deployed and tested successfully against preconfigured oc4j. I always believed that copying the system-jazn-data.xml from C:\Documents and Settings\
\Application Data\JDeveloper\system11.1.1.0.22.47.96\o.j2ee\embedded-oc4j\config (for embedded oc4j) to C:\Documents and Settings\\Application Data\JDeveloper\oracle.adfp.seededoc4j.11.1.1.0.0.071218.1800\j2ee\home\config (for preconfigured oc4j), which made it stronger, especially after few experts responded that I was on the right track.
After careful comparison of my actual project with the sample application, I did find that, jps-config.xml and orion-application.xml in the /src/META-INF, did not contain key information like realm, identity store and policy store information. I was particularly surprised to learn that, the same set of files did not have any issues while being used with embedded-oc4j. Hence, I replicated the same onto my main project, after which the authentication was fine.
I had expected that, since system-jazn-data.xml contains the permission information at the pageDef level, authorization should be fine after migration. I verified that authorization was fine too, after migrating to preconfigured oc4j.
I have deployed and tested these on a standalone oc4j using ant script, and it works fine there as well.
No comments:
Post a Comment