ApEx Listener 2.0, non-ApEx application
jflackNov 28 2012 — edited Jun 17 2013I've been successfully using the ApEx Listener 1.1.4 to reach my non-ApEx Web PL/SQL (OWA) applications.
So I decided to try the new ApEx Listener 2.0 EA2 with this - I was especially interested in multiple database capability, so I only have to deploy one copy of ApEx Listener.
2.0 is lousy for non-ApEx. For one thing, you CAN'T use SQL Developer to administer the thing without having it pointing at an ApEx WITH restful services - it even seems to expect ApEx 4.2. But there are no web-based configuration screens anymore, so the only other way to configure it is to do "java -jar apex.war +subcommand+". That assumes that you have command line privileges on the server that is hosting your ApEx Listener. I can get this, but WHY should I need to?
Please Oracle, re-think the administration of this version of the listener before you go to production. I don't want to run ApEx, I don't really want to unlock APEX_PUBLIC_USER, or create the APEX_LISTENER or APEX_REST_PUBLIC_USER accounts, or update my ApEx (that I don't use) to 4.2. I just want a replacement for mod_plsql, so I can run everything on WebLogic instead of old OAS.