Please change your user handle from "2940684" to something meaningful. Refer : Video tutorial how to change nickname available
I have several Apex 4.2.5 applications that were front ended by modplsql. In the dads.conf file there were multiple Alias statements used (/i/ , /epmimages/, /buttons/, /pbimages/, /ux/ ) each with their own respective directory paths. I am moving them to new servers front ended by Oracle Rest Data Services. I have moved the /i/ (apex) images using the "static" command with java -jar ods.war ... and those images are being served properly. I don't know how to configure ords to have the equivalent structure for the other modplsql "Alias" resources. I am testing in standalone mode, but will move it to glassfish for production. Can anyone point me in the right direction?
What is the ORDS version you are using?
You can create static images reference with different context path referencing different directories on your web server and then you can deploy it to Glassfish Server(same as you deploy i.war).
So basically you can give the following commands to generate wars for:
- /i/ (i.war) :
java -jar ords.war static /path/to/apex/images
java -jar ords.war static --context-path /i /path/to/apex/images
- /epmimages/ (epmimages.war) :
java -jar ords.war static --context-path /epmimages /path/to/epmimages
- /buttons/ (buttons.war) :
java -jar ords.war static --context-path /buttons /path/to/buttons
- /pbimages/ (pbimages.war) :
java -jar ords.war static --context-path /pbimages /path/to/pbimages
- /ux/ (ux.war)
java -jar ords.war static --context-path /ux /path/to/ux
Then you can deploy these war files as you will deploy i.war to Glassfish Server.
Hope this helps!
Personally, I would just put the directories under the docroot of the webserver. Using the i.war , abc.war method means any change to a file or new file means new war file and deployment. Where if they are just in the docroot, you just make the changes to the files.
( Also we're going to remove the ABC.war for this reason )
I'm curious about your comment that you'll be removing "...the ABC.war for this reason". Are you saying that you're going to change the method of how ORDS is going to be deployed to app server containers? I'm curious, if you can say, what the alternative might look like?
I have following queries:
- The title says "Configuring a Doc Root for Non-Application Express Static Resources", so your answer regarding docroot given above to OP still stands?
- Can docroot be any directory on web server or has to be specific directory viz. /var/www/html?
- Will ORDS be able to serve the files in the docroot in Oracle APEX applications? (as it serves for /i/)
- The first line in the above documentation reference says "You can configure a doc root for standalone mode". So, is the docroot restricted only to standalone mode or can it be used with ORDS deployed to Supported Java EE Application Servers? If yes, how can we can we configure docroot for Supported Java EE Application Servers?