#Oracle XE & APEX The goal of this project is to make it easy for developers to quickly build and/or launch a fully functional instance of Oracle XE and APEX. The code provided in this project handles the automatic build. There is also a listing below of prebuilt images for popular cloud providers.

Note: Currently these machines aren't ready for production as they lack backup scripts, SSL encryption for APEX, etc. These features will be implemented in future releases

#Supported OS's This script currently works on the following operating systems

CentOS 7

#Download

#Note It helps to run all the scripts as root
#sudo -i
cd /tmp
yum install git -y
git clone https://github.com/OraOpenSource/oraclexe-apex.git
cd oraclexe-apex

##Configure You then can optionally modify the config file to change the default installation options.

#Look for "CHANGEME" in this file
vi config.sh

###APEX There are additional APEX configurations that you may want to make in the scripts/oracle_config.sql file. You can run them later on or manually configure them in the APEX admin account.

##Build To build the server run the following commands. It is very important that you run it starting from the same folder that it resides in.

#Eventually you will be able to do the following
#Dependent on issue #2
. build.sh

#For now you must open build.sh and run each section manually
#This is do to an ORDS issue that doesn't allow for silent install. Once fixed you won't need to run each section manually

#Prebuilt Images The goal of this project is to have prebuilt images for major cloud providers.

TOOD list of prebuilt images for different cloud platforms

#How to connect

##Oracle / SQL*Plus Since direct connections to the database aren't encrypted you will need to tunnel your connection over SSH. Jeff Smith has a good example on how to connect using SQL Developer.

By default a user called OOS_USER (password: oracle) has been created.

Username	Password	Comments
OOS_USER	oracle	User you can use to develop with right away
SYS	oracle
SYSTEM	oracle
APEX_PUBLIC_USER	oracle

##APEX To connect to APEX go to http://<server_name>/ and it will direct you to the APEX login page.

Workspace	Username	Password	Comments
INTERNAL	admin	Oracle1!	Workspace administor account
OOS_USER	oos_user	oracle	You can start developing on this account. It is linked to OOS_USER schema

###APEX Web Listener This project uses Node4ORDS as a web listener. The Node4ORDS project provides the ability to server static content and will provide additional web server functionality. Please read its documentation for more information.

Node4ORDS is install in /var/www/node4ords. It can be controlled by:

/etc/init.d/node4ords start
/etc/init.d/node4ords stop
/etc/init.d/node4ords restart
/etc/init.d/node4ords status

Static content can be put in /var/www/node4ords/public/ and referenced by http://<server_name>/public/<filepath>

###ORDS ORDS is located in /ords

The APEX images are stored in /ords/apex_images

##Tomcat Manager This server uses Apache Tomcat as the web container for ORDS. By default, the firewall restricts public access to the Tomcat server directly. If you do want to make it accessible run:

service firewalld start
firewall-cmd --zone=public --add-service=tomcat

You can then access Tomcat via http://<server_name>:8080 and Tomcat Manager via http://<server_name>:8080/manager

Username	Password	Comments
tomat	oracle	Admin account

By default the admin account is tomcat/oracle

To disable Tomcat firewall access run: note: if you don't disable it, the next time the server is rebooted it will be disabled.

firewall-cmd --zone=public --remove-service=tomcat

Tomcat is located in /usr/share/apache-tomcat-7.0.57/. Note that the location may vary depending on version number. It can be controlled by:

/etc/init.d/tomcat stop
/etc/init.d/tomcat start

#Port Configurations The default port settings are as follows:

Port	Service	Open	Comments
22	SSH	Yes
80	Node.js	Yes	HTTP Server
1521	Oracle SQL connection	No
8080	Tomcat	No
8081	PL/SQL Gateway	No	Disabled by default

#Other ##Editing server files locally To make it easier to edit files on the server (and avoid using vi), Remote-Atom (ratom) is installed by default. This requires that you have the Atom text editor on your desktop and have installed the ratom.

When you connect to the server use the following connection string:

ssh -R 52698:localhost:52698 root@<server_name>

Note: Port 52698 is the default port and can be changed in the plugins settings in Atom

Once you're connect to edit a file locally simply type:

ratom <myfile>

The file will then appear in your Atom editor.