Thursday, August 09, 2012

Oracle APEX Listener 1.x vs 2.0

The new Oracle APEX Listener 2.0 Early Adopter is publicly available now.
If you compare it to the current production version these are the most changed or new features.

Configuration

APEX Listener 1.x: the configuration screen to tell the listener in which database APEX is installed

APEX Listener 2.x: either you configure the listener through command line

Command line configuration of the APEX Listener 2.x
or through SQL Developer 3.2 or higher (currently not publicly released yet)

Configuration through SQL Developer 3.2
So the web interface is gone in the APEX Listener 2.x... As you can see in the screenshot, you can now configure multiple databases. Before you had to configure multiple APEX Listeners; one for DEV, one for TEST, one for Production etc. Now you can just have one APEX Listener routing to the correct database.

Another new feature is that you can route multiple url's to different APEX applications.

Resource Profiles (aka RESTful Services)

APEX Listener 1.x; you define Resource Templates through the web interface


APEX Listener 2.x; you can now configure the RESTful Services through a patched APEX 4.1.1 or native in APEX 4.2. The following screenshot shows how it looks like in a patched APEX 4.1.1 version.



New in the APEX Listener 2.x is RESTful OAuth 2.0 integration.

New features

More configuration options.


Integration of ICAP virus scanner, so when a file gets uploaded to your database, even before it hits your database it can be scanned.


More features are there to come, for example integrated FOP support...

I hope you see that Oracle is putting a lot of effort in the APEX Listener... it fits in the proof of the additional features you get with the APEX Listener I mentioned in my previous post "Moving to the APEX Listener".

3 comments:

Matthias Hoys said...

Interesting to know that you can now connect to multiple databases. However, I often find it useful to fully separate the different environments. This way you can upgrade one environment without affecting the other. Well, I guess both options have their advantages. It's good that now there is the flexibility to choose.

Walid Saliba said...

You mention that "Another new feature is that you can route multiple url's to different APEX applications.". Could you indicate how & where this configuration is made?

Thanks

Dimitri Gielis said...

if you mean rerouting to other databases/apex; see http://docs.oracle.com/cd/E37099_01/doc/doc.20/e25066/config.htm#autoId5

Kris Rice also did some blogposts about this http://krisrice.blogspot.be/2013/07/nicer-urls-for-apex-yet-another-option.html