Skip to main content

Setting the starting point for KScope2011: Get XFILES running...

By
As a preparation for a joint presentation with Marco Gralike for ODTUG Kaleidoscope 2011, I tried to (re)install the not-yet-so-famous XFILES Application. That application was the result of the collaboration of Mark Drake (Sr Product Manager XMLDB) and Carl Backstrom. They did a presentation about it during OOW2008. The idea behind the presentation/application was leveraging the power of XML-DB with an APEX UI. Due to Carl's tragic car accident, the application never reached a final stage. Marco already did a sequel about XFILES on his blog. You can also find a download link to the latest version of the application there.
But back to the installation....I used the OTN Developer Days VM as a start and patched it with the latest APEX patch (4.0.1). There is a sort of how-to included in the XFILES download, but that isn't flawless (yet). But after executing all the steps I fired up the application and got this:


So all my images where missing. Inspecting the code learned that the images had a path of /XFILES/APEX/lib/icons/, so not pointing to images included in the application itself (as Application or Workspace Images) but to a directory on the filesystem....that wasn't there.  If I entered http:/localhost/XFILES I did get the directory listing. And drilling down I could see the images. After some investigation it turned out that localhost was using the standard port 80, which was used by the (standard installed - or done by the XFILES installation ??) Embedded PL/SQL Gateway (EPG). And I was using the Apex Listener (with Apache/Tomcat) on port 8888. So the APEX Listener was looking for the XFILES directory on it's root (/home/oracle/apache-tomcat-6.0.20/webapps/ROOT). So in order to get the images in my application I could just extract them from the XDB Repository and copy them onto the filesystem. But that would have been too easy ;-). I though it would be more fun if I could create a mapping from the right location on the filesystem into the right location in the XDB Repository! But as I am not a *nix wizard - nor a XML-DB guru -, I couldn't quite figure out how to do that - even after some Googling around . So I send out a "help Tweet". But it is hard to explain a situation in just 140 characters...
Nevertheless I got a lot of replies (thanks Learco, Iloon, Jacco, Peter, etc). But Marco acted as my mainstay and Skyped me. And just like Marco is, he dived in deep and came up with a solution! And wrote a long post about it...
But in short there are only two additional steps necessary:
1. Create the XFILES directory on the webserver :
/home/oracle/apache-tomcat-6.0.20/webapps/ROOT/XFILES
2. As su, mount the XFILES Folder in the XDB Repository to that directory:
mount -t  davfs  http://localhost:80/XFILES /home/oracle/apache-tomcat-6.0.20/webapps/ROOT/XFILES

And the result is:


The funny thing about this solution is, that I - as a user - can replace one of the images with my own one and it will immediately show up in the application itself:


Now I first have to solve a performance problem, because the app is deadly slow... Maybe just because of this solution? Don't know yet, will have to find out!
After that the next step is to make it a full blown APEX 4.0-style application, before moving on...
Labels:

Comments

Roel said…
I am already convinced that the "map Unix directory to XDB folder" doesn't speed up performance... If I replace the mounted directory with a real one, the response time increases dramatically...
1:54 pm
Post a Comment

Popular posts from this blog

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more

APEX ReadOnly Pages - The easy way

By
If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...
Post a Comment
Read more