The Oracle Application Express architecture requires some form of Web server to proxy requests between a Web browser and the Oracle Application Express engine. So far you had following possibilities:
- Oracle HTTP Server/mod_plsql
- XDB HTTP protocol server/embedded PL/SQL gateway
It's an alternative that is offered for the above two and with APEX 4.0 it will become the first choice.
Below you see a slide of the APEX 4.0 presentation. It explains what happens more graphically.
The main reasons why you want to consider the APEX Listener:
- it supports file system caching
- it makes the printing of pdfs easier as the APEX Listener is build in Java and integrates nicely with FOP.
- support of multiple file upload, the architecture of mod/plsql didn't allow that
- you can add your own plugins to it
- it has a workload capture feature
5 comments:
But, will we be able to integrate NTLM authentication with the new listener?
Without that, I think a lot of people will not be all that interested.
What about drawbacks ?
Are there any ? Can SSL be used for example ?
I don't know whether my question is linked with this blog. We're developing a system using Oracle APEX (version >3.2) and we want to use NTLM authentication. How can we use mechanism? We've an NTLM.jar file for our existing system and we would want to use the same .jar file in this new APEX based application after modifying code in some of the .java files in that JAR. Can we really make it possible?
It would be great if you could suggest something in this.
Himanshu
Speaking of file upload. I would like to switch to a new listener with tomcat but there is a file upload problem. I’ve got a working application on apache/embedded listener but with a new listener a file is not uploaded and a file name is not passed to the file upload procedure. Would you know what the issue is?
Thanks,
Art
Post a Comment