Embedded Files
For Tomcat installs the configuration files will be under:
/tomcat/latest/conf/ords.For Standalone installs they will be under:
/tomcat/ords/conf/ords
defaults.xml
defaults.xml
<entry key="cache.caching">false</entry>
<entry key="cache.directory">/tmp/apex/cache</entry>
<entry key="cache.duration">days</entry>
<entry key="cache.expiration">7</entry>
<entry key="cache.maxEntries">500</entry>
<entry key="cache.monitorInterval">60</entry>
<entry key="cache.procedureNameList"/>
<entry key="cache.type">lru</entry>
<entry key="debug.debugger">true</entry>
When this is set to true, detailed logging information is appened to (TODO)This setting should not be enabled on production systems due to the performance impact of outputting large amounts of data to the log.<entry key="debug.printDebugToScreen">true</entry>
When this is set to true any error (shown in your browser) includes a detailed message and stack trace. This setting must not be enabled on productions systems due to the risk of sensitive information being revealed to an attacker.<entry key="error.keepErrorMessages">true</entry>
<entry key="error.maxEntries">50</entry>
<entry key="jdbc.DriverType">thin</entry>
<entry key="jdbc.InactivityTimeout">1800</entry>
<entry key="jdbc.InitialLimit">3</entry>
<entry key="jdbc.MaxConnectionReuseCount">1000</entry>
<entry key="jdbc.MaxLimit">10</entry>
<entry key="jdbc.MaxStatementsLimit">10</entry>
<entry key="jdbc.MinLimit">1</entry>
<entry key="jdbc.statementTimeout">900</entry>
<entry key="log.logging">false</entry>
<entry key="log.maxEntries">50</entry>
<entry key="misc.compress"/>
<entry key="misc.defaultPage">apex</entry>
<entry key="security.disableDefaultExclusionList">false</entry>
<entry key="security.maxEntries">2000</entry>
url-mapping.xml
url-mapping.xml
<?xml version="1.0" encoding="UTF-8"?>
<pool-config xmlns="http://xmlns.oracle.com/apex/pool-config">
<pool name="mysid" base-path="/mysid" updated="2022-02-04T15:01:48.297Z"/>
</pool-config>
Will have an entry for the target database of your ORDS installation. If you target multiple instances then this file will have multiple entriesstandalone.properties
standalone/standalone.propertiesstandalone.properties
These settings are only relevant if you start the ords.war in standalone mode (e.g. for troubleshooting).Remember that standalone mode is supported but not recommended for production workloads.
jetty.port=9090
Port. If ORDS is also running under Tomcat on this server then this port should not clash with the Tomcat port.standalone.context.path=/ords
standalone.doc.root=/tomcat/latest/conf/ords/standalone/doc_root
standalone.scheme.do.not.prompt=true
standalone.static.context.path=/i
Defines relative path of the images directory. In this case: /tomcat/latest/webapps/iPage updated
Google Sites
Report abuse