Oracle XE / APEX Build Script 0.2.0 Released

We're pleased to announce that today we released the 2nd minor release (0.2.0) for the Oracle XE / APEX build project: Though this was a minor release they're a lot of great new features added to the build scripts.

Vagrant: Vagrant is a tool for building development environments. The build script now supports it and additional documentation is found on main page Github page.

Demo Data: By default if the user is created (managed by OOS_ORACLE_CREATE_USER_YN in the demo EMP and DEPT tables will be created. To disable the creation of demo data modify the OOS_ORACLE_CREATE_USER_DEMO_DATA_YN configuration option.

If you want to install the demo tables at a later time you can manually run oracle/emp_dept.sql.

Firewall: To help secure the server, we only open ports 22 (SSH) and 80 (APEX/Web Server). Some people asked for the ability to open port 1521 to connect to Oracle using SQL*Plus. You can now enable this as part of the coniguration with the OOS_FIREWALL_ORACLE_YN option. Note: if you do open this port and connect to it, your communications are not secure as it is not an encrypted connection. If you access over a public network this is a huge security vulnerability so you should connect using SSH tunnelling. We'll blog about this soon.

rlwrap: rlwrap is now installed on the server. This will help if you need to use SQL*Plus on the server. The following blog post covers how to use it:

Create User Script: By default the build script creates a user called OOS_USER. If you want to create new users you can now reuse the same script we do: oracle/oracle_create_user.sql. It currently takes in 3 parameters: Username, Password, and Y/N create demo data. More help can be found in the file.


Besides the new features, this release is significant in that it will be the last release to support pre-APEX 5 installations as APEX 5.0 was released today. Sign up for our email list to be notified when we have it integrated APEX 5.

Some people have also asked us about SSL support as it's a major requirement to run the server with public content. We are aware of this request and already have an issue logged. We're waiting for Let's Encrypt to be released so that it's easy to add a SSL certificate.