Mark wrote:with reference to this, I've no experience with it, but from what I've read, the Apex Listener can handle non-Apex mod_plsql connections. It may be worth investigating this.
As I said, APEX listener is only for APEX applications. If you have PL/SQL web toolkit applications I do not think it will work, it requires OHS/mod_plsql.
Mark wrote:I did some searches on the Apex Listener forum as well as good ol' google.
Hi Vite DBA
I will research this. Do you recall where you read this at.
My understanding was apex listener is for apex applications only.The Apex listener runs completely separate to the database as a Java app, in fact there would be nothing stopping you running OHS and the Apex listener side by side with different port numbers. The only problem I would see is that the Apex Listener has more inbuilt features around web services etc that if incorporated in an app wouldn't be available when running the same app through OHS.
There are couple of issues too using apex listener is that can only run inside the database so you cant separate the web server machine from DB machine.
I think also performance wise OHS is much better and robust than apex listener.I'm not speaking from personal experience, but from what I gather, there are no major performance problems with the Apex Listener. From a robustness point of view, true, the OHS is built on a very solid foundation in the Apache space, but the Apex server is now up to version 2.0 and once again I haven't heard anything too detrimental.