Databases Reference
In-Depth Information
<entry key="apex.cache.monitorInterval">60</entry>
<entry key="apex.cache.directory">/var/folders/mN/mNPteN52HoqHK2miZ4o6IU+++TU/
-Tmp-/apex/cache</entry>
<entry key="apex.procedure.preProcess"></entry>
<entry key="apex.procedure.postProcess"></entry>
<entry key="apex.misc.defaultPage">apex</entry>
<entry key="apex.misc.compress"></entry>
<entry key="apex.debug.debugger">false</entry>
<entry key="apex.debug.printDebugToScreen">false</entry>
<entry key="apex.error.keepErrorMessages">true</entry>
<entry key="apex.error.maxEntries">50</entry>
<entry key="apex.log.logging">false</entry>
<entry key="apex.log.maxEntries">50</entry>
</properties>
Now I'm not going to go through all the options here; many of them should be obvious (for example,
the hostname and SID). This also illustrates how you can update the configuration directly without
going via the GUI. (You could potentially even generate the configuration file automatically through a
script.) The setting I am interested in here is
<entry key="apex.misc.compress"></entry>
We can change that to:
<entry key="apex.misc.compress">true</entry>
to enable compression.
Now you need to restart the APEX Listener, but this time you'll want it to use your current
configuration file. You can do that by examining the options available with the
apex.war
file by providing
the
-help
parameter:
[jes@ae1 listener]$ java -jar apex.war --help
java [options] -jar apex.war [--help]
Options:
-Dapex.home=/path/to/apex : Path to the folder used to store the
web container runtime, defaults to:
${java.io.tmpdir}/apex
-Dapex.port=nnnn : HTTP listen port, default 8080
-Dapex.ajp=nnnn : AJP (mod jk) listen port, default none
If an AJP Port is specified then HTTP access is disabled
-Dapex.images=/images/location : Path to the folder containing static
resources required by APEX
-Dapex.erase=true : Erase the contents of ${apex.home}
before launching
--help : Print this usage message
You should now be able to restart the Listener and confirm that compression is indeed occurring.
Hopefully at a future time this option will be configurable through the GUI configuration itself.
