AAAAAAAAAAAAAAARRRRRRGGGGGHHHHHHHHH!!!!!!!!!!!!!!!!!!!!!!!!!!!! I feel better now
Well I came back to my APEX / Glassfish set-up ready for some development, and got confronted with
HTTP Status 503 – Requested url https://x.x.x.x:8181/apex/ is currently unavailable.
It turns out that the listerner file is only held in a temporary area, WHY??????????
The file is called apex-config.xml and is found at /tmp/apex/apex-config.xml
Now I could copy the file and at reboot, copy the file back to this location but there must be a better way.
There are a couple of ways
The first way is to edit the web.xml file that is unpacked when deployed by the Glassfish server.
remove the comment lines <!– –> from around the this section of the file
You must start and stop the Glassfish server
Now you just have to navigate to the listenerConfigure URL and re-input the details
See the listener configuration section in Installing a Glassfish Server for APEX access in Amazon AWS
Just as a reminder 🙂
To access Oracle Application Express Listener Administration, in your Web browser go to:
This will create the apex-config.xml file in the user’s home directory that starts the Glassfish server. You could even copy this away for safe keeping.
The second way of changing these settings is to unpack the apex.war file, change the web.xml file. Re-pack the war file and then redeploy the apex.war file via Glassfish. You can do this if you like, but I am not expert in Java, and unpacking and packing files for deployment. I am sure that there is valid reason for doing this, but at the moment I don’t care :). I have a working environment at that is what matters.