This content has been marked as final. Show 3 replies
the APEX Listener itself is stateless, so you can cluster it easily if you want or have to.
APEX Listener is licensed with APEX, not with WLS. You can use a variety of J2EE containers that meet the requirements. In addition to WLS, Oracle supports the use of OC4J (either part of OAS or standalone) and GlassFish. In fact, the APEX Listener ships with an embedded version of GlassFish.
Despite the support aspect, there are people who successfully run the Listener on the GlassFish's Open Source Edition or Apache Tomcat.
Concerning your SLAs: The Listener will do something for you, so of course it will need the CPU. How much load it will generate depends on your usage scenario. Your post sounds like you already use APEX with a different web server than the Listener. If that guess is right, it would be helpful to know which web server you use now and how much CPU time it consumes.
Thanks UDO. So if you do decide to use the APEX Listerner with Weblogic you would have to license the APEX listener and Weblogic. Is that a fair assumption.
just to make that clear again: there is no separate license for the APEX Listener. It is (currently) always licensed with APEX, which again is always licensed with any database version. So in your case, it's only the WLS that you need to care about.