What ORDS Standalone is
ORDS Standalone webserver which is Eclipse Jetty, https://eclipse.org/jetty/ . For the standalone, ORDS sends output to STDOUT, it runs on the command line. That means there's nothing like a control commands like startup, shutdown,status nor log files, access logs. It's bare bones intentionally to get up and running fast. Then it's recommended for anything with lots of volume more to a more full featured webserver like Tomcat or WLS.
Standalone Startup
With all that said, it is quite simple to use the standalone for most cases. When doing this the most important thing is just a startup script so that when the machine/db starts the ORDS instance starts also. There's an init.d script in this blog post that can be used and adjusted as needed : http://krisrice.blogspot.com/2010/12/listener-startupshutdown-script.htmlStandalone Access Logs
The other thing much needed from a standalone instance of ORDS would be an access log to see what it's getting for traffic. Here's where being Jetty based is a great thing.This is documented for some solaris workaround only so probably missed by most. ORDS Standalone allows for customization of the Jetty server itself. Looking at the ords configuration directory there's a <path>/standalone. This will have a file named standalone.properties which looks like this which is the name/value pairs of what ORDS will configure.
#Thu Jan 12 09:56:19 EST 2017 jetty.port=8081 standalone.access.log=/tmp/ords_log standalone.context.path=/ords standalone.doc.root=/Users/klrice/workspace_ords_3.0.x/klr_vm_config/ords/standalone/doc_root standalone.scheme.do.not.prompt=true standalone.static.context.path=/i standalone.static.do.not.prompt=true standalone.static.path=/Users/klrice/workspace/apex_trunk/images
Jetty is configurable by xml documents and the documentation has some really good example of what's possible. This blog post is going to focus on the Access Log section here: https://eclipse.org/jetty/documentation/current/configuring-jetty-request-logs.html
In that same directory, create a folder named "etc" and in there create a file named "jetty-http.xml" . Then drop this into the file
<?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd">
<Configure id="Server" class="org.eclipse.jetty.server.Server">
<Ref id="Handlers">
<Call name="addHandler">
<Arg>
<New id="RequestLog" class="org.eclipse.jetty.server.handler.RequestLogHandler">
<Set name="requestLog">
<New id="RequestLogImpl" class="org.eclipse.jetty.server.NCSARequestLog">
<Set name="filename"><Property name="jetty.logs" default="/tmp/"/>ords-access-yyyy_mm_dd.log</Set>
<Set name="filenameDateFormat">yyyy_MM_dd</Set>
<Set name="retainDays">90</Set>
<Set name="append">true</Set>
<Set name="extended">false</Set>
<Set name="logCookies">false</Set>
<Set name="LogTimeZone">GMT</Set>
</New>
</Set>
</New>
</Arg>
</Call>
</Ref>
</Configure>
Now when ORDS is started again you'll have a file that was specified in the xml file. This example is /tmp/ords-access-2017_01_12.log with an normal NCSA/Apache looking access log.
0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:32 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:33 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:33 +0000] "GET /ords/klrice/test/morse?text=3362 HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:33 +0000] "GET /ords/klrice/test/morse?text=5728 HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:34 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx.%29%29%22%29.%28%2C%27%2C HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:34 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%27jSwGPl%3C%27%22%3EbBKXcr HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:34 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%29%20AND%208651%3D9722%20AND%20%289950%3D9950 HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:34 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%29%20AND%203741%3D3741%20AND%20%285130%3D5130 HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:34 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%20AND%204853%3D4504 HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:34 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%20AND%203741%3D3741 HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:34 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%27%29%20AND%201525%3D5863%20AND%20%28%27aKGY%27%3D%27aKGY HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:34 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%27%29%20AND%203741%3D3741%20AND%20%28%27jcNS%27%3D%27jcNS HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:34 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%27%20AND%204691%3D5794%20AND%20%27rhDV%27%3D%27rhDV HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:34 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%27%20AND%203741%3D3741%20AND%20%27FJPb%27%3D%27FJPb HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:35 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%25%27%20AND%206423%3D5178%20AND%20%27%25%27%3D%27 HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:35 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%25%27%20AND%203741%3D3741%20AND%20%27%25%27%3D%27 HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:35 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%20AND%209677%3D8181--%20embz HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:35 +0000] "GET /ords/klrice/test/morse?text=de%20n1jlx%20AND%203741%3D3741--%20ldng HTTP/1.1" 200 - 0:0:0:0:0:0:0:1 - - [12/Jan/2017:15:22:35 +0000] "GET /ords/klrice/test/morse?text=%28SELECT%20%28CASE%20WHEN%20%284135%3D9257%29%20THEN%204135%20ELSE%204135%2A%28SELECT%204135%20FROM%20INFORMATION_SCHEMA.PLUGINS%29%20END%29%29 HTTP/1.1" 200 -
Summary
Here's the simple steps:1- mkdir <ords config directory>/standalone/etc
2- vi jetty-http.xml
3- paste the above xml file and adjust the log location
4- Restart ORDS
