This content has been marked as final. Show 3 replies
I put my summary first before I go through your post in detail:
What you see tells me your instance "works as intended". The availability of APEX themes might be a bit confusing if you don't know much about the technical backgrounds of APEX yet.
I can only see one Theme under Shared Components/Themes, Scarlet-21This is not very unusual. You'll only see the theme you've selected when you created your application (or the default theme). You should see all themes available in APEX when you run through the "Create Application" wizard, e.g. when you reach step 10 as described in [url http://docs.oracle.com/cd/E23903_01/doc/doc.41/e21674/bldapp_wiz_using.htm#CEGEIHJF]Application Builde User`s Guide.
I can see all the Images when I login into ApexThen your APEX Listener is working fine.
In the images folder there are plenty of themes, but for me it looks like Apex cannot find them.APEX doesn't have (or need) access to your web server, including APEX Listener. There is no functionality to validate if you have all files for your themes on your web server. I'd even say this can't be done, because you could put a proxy in front of your web server hosting APEX (which could be APEX Listener, but also the Embedded PL/SQL Gateway or OHS or any of the three at the same time...) that serves the static contents, so there would be no way to implement such a check.
I read somewhere, that I can see the themes folder in the browser with http://localhost:8080/i/, but I get only a not-found-Message and Grizzly.I don't know where you read that, but there is no index file in the images folder. Perhaps your source used OHS and configured it to provide directory listings (e.g. with option +indexes), but it's nothing APEX Listener would provide in Standalone Mode, so there's nothing wrong here as well.
I do not where the alias for the image folder is stored? Is there a config file?The alias is always +/i/+ when you run APEX Listener in Standalone Mode. Note that the images prefix in APEX has to be set to that value to get/keep APEX working. Nothing to worry about, as it is the default and obviously configured that way in your scenario.
The directory the alias points to in Standalone Mode is the one you've configured with the option -Dapex.images in your startup. It seems to work fine, as mentioned before. But to answer your question properly: There is a config file named apex.properties in your APEX Listeners home directory that stores the value configured for the images directory in Standalone mode.
Another side note:
java -Dapex.images=C:\oracle\product\apex\images -Dapex.home=erase -jar apex.warYou set apex.images to a proper path. Do you really want to set apex.home to erase ? I'd recommend to use a regular and meaningful path for this. Derived from your images directory this could be something like C:\oracle\product\apex_listener\conf.
I hope I could help to clarify a few things on how APEX Listener works.
Thank you, very much for your detailed explanations, it helped.
The problem was not a listener problem, it was in front of the keyboard. When I created a new application, I always selected 'yes' when coming to the step 'Copy shared component from another application', because I thought I had to copy an existing builtin theme. Now I selected 'no' and finally got to see all the buildin themes. Wonderful.
It took me a lot of nerve, but I learned a lot about the listener - the hard way.
P.S: -Dapex.home=erase was a typo, I used -Dapex.erase=true.
I'm glad to hear you now find your APEX environment working as expected.
Learning is a lifetime challenge for everyone of us - nobody is born with all omniscience. ;)
P.S.: Thanks for marking this question as answered. Please also think about marking helpful or correct answers accordingly so other users searching for a similar issue can spot relevant posts easily. Thanks!