KScope15 day 2 (06/23/2015)

Session 5 (8:30am-9:30am) Dimitri Gielis How to make APEX Print through node.js
Key points:

• Node.js is a server that runs in Javascript
• Demo of officegen, an XML generator which runs on node.js.
• Demo of APEX Office Print, AOP (produce DOCX,PPTX,PDF from within APEX)
• It is possible using javascript to print directly to a printer

Session 6 (9:45am-10:45am) Matt Nolan FOEX Vendor Presentation: Build complex app in APEX 5.0 with ease, using FOEX and the new page designer
Key points:

• Thanks Matt for showing us how awesome FOEX is.  It is really neat to see how fast you can develop a very rich page with FOEX.

Session 7 (11:15am-12:15am) Martin D'Souza Top 10 APEX API
Key points:

• OraOpenSource.com contains great APEX utilities.
•  sleep/pause, stop_apex_engine
• string_to_table (useful for delimited lists)
• api.oracleapex.com

Session 8 (2:00pm-3:00pm) Alex Nuijten and Alan Arentsen APEX, Node.js, and HTML5: Magic!
real time process control with APEX5, and a Lego Mindstorms running Linux and Node.js

Key points:

• It really is neat to see what you can do with APEX, Linux, and node.js

Session 9 (3:30pm-4:30pm) Tim Austwick and Nathan Catlow APEX Security: Hack Demos and Security Best Practices
Key points:

• Should be running ORDS2.0.8+.
• Should be running APEX 4.2.6+.
• SSL should be enabled and should only be allowing HTTPS.
• Should define security inclusion list (f,p,z,wwv_*, apex*).
• Buttons and processes must have the same conditions as the page.
• Avoid substitution syntax, as this is exploitable, even with code commented out.
• Avoid dynamic SQL statements.
• Escape your HTP.P calls.
• Safest to not even have the APEX builder installed in a production environment.
• APEXSEC is an application which helps find vulnerabilities in your application.

Session 10 (4:45pm-5:45pm) Dietmar Aust Setting Up the Oracle APEX Listener (Now ORDS) for Production Environments
Key points:

• Reference architecture = Apache HTTPD 2.4 reverse proxy - AJP - Tomcat 8 (ORDS 3) - JDBC - Oracle DB (APEX 5.0).
• The WORK is done IN THE DATABASE.
• The webserver and PL/SQL gateway don't need alot of processing power, most of the time idle.
• Install in a layered approach, testing along the way to make sure each layer works.
• Configure ORDS in standalone mode, then TEST it.
• Deploy ORDS to Tomcat, then TEST it.
• Configure Apache HTTP server as a proxy to Tomcat, then TEST it.
• Must optimize the connection pool.
• Monitor: select username, status, count(*) count from v$session where username LIKE '%APEX%' OR username LIKE '%ORDS%' group by username, status;
• Can test the tomcat installation http://localhost:8080/i/apex_version.txt.
• See slides, as they are full in reference material.