Roel Hartman and me are currently very busy with our Kaleidoscope 2011 presentation “XFiles, the…
Had my adventures today. Most of the packages are compile and the XDB utility packages are in place (will come back on those in a later post). Apparently as said before, Mark has added some extra new functionality “Application Security” for use with APEX. This almost locked me out today after bringing into place all the packages, dependencies etc. While almost finished, my APEX “admin” account was locked out. I did a reset of the admin password but then I got the neat security message: “Access denied by Application security check. Application access restricted to internal workspace users.“. Oops.
Although…Its actually cool …
Hacked my way in via amongst others resetting the admin password again and xdbconfig.xml content that controls the (as it is called in the APEX domain) PL/SQL Gateway (aka the XMLDB Protocol Server).
I don’t think a lot has changed to the application since Carl and Mark worked on it, besides the now build-in Application Security part (Managing XML Content with Oracle XML DB and Oracle Application Express). I didn’t cross-reference it yet with the “original” from OOW 2008, checking it via my old pictures of the presentation in 2008
Anyway. So does it look like? Have a look at the following pictures.
You might have already seen the web page in my earlier post. It also enables you to login using a defined “Application Principle” account.
Click on the picture to enlarge
Its not yet “the breeze” I hoped for in regard to “Installing XFiles” on APEX. I am missing parts of the source that XFiles in APEX is build upon and although I know where I can get it, it is not easy to implement it “The APEX” way. For example XFiles is depending on XDB Utilities, packages and methods in PL/SQL, that makes life easier while working with XMLDB and/or have implemented some of the best practices ideas of the XMLDB Development team and others. To do it, installing those, the “neat way”, it should be created in a different Oracle schema and not in the APEX workspace user owner (other database schema’s might enjoy them as well in the database).
A DBA View on Things…
APEX doesn’t have, AFAIK as a newbie, yet a proficient way to make this easy to install, or at least what I thought could be done, via a single packaged install. First of all, as said, there are dependencies to other “outside” packages and privileges. APEX doesn’t checks this but just fails and show a nice report with the failed statements (nice implementation) but would it not be even nicer to have a pre and post installation workspace import pages that checks on criteria needed and/or set by the creator of the APEX application before and afterward, the workspace SQL file is even imported. Ever have used, for example the latest, Oracle Software installer… That kind of thing but be a nice asset. There is now to much stuff, I hope that I actually implement correctly / as the APEX application creator, mend it to be.
An example. Apparently this XFiles demo application has been progressed in his source since the mentioned OOW 2008 Mark & Carl demo. It needs the database compatible parameter to be set to0 Oracle Database version 188.8.131.52.0 to actually work in respect to demonstrated the Application Security for APEX build upon XMLDB Access Control List Security (ACL’s) features, as demonstrated by Mark during Oracle Open World 2009 (Managing XML Content with Oracle XML DB and Oracle Application Express).
The first page, the XFiles APEX login page, hints this security feature implemented (check box with “Application Principle”)…
Click on the picture to enlarge