This content has been marked as final. Show 6 replies
it seems you are using the APEX Listener in Standalone Mode.
It would have been helpful to know how you started your APEX Listener. Probably you didn't configure the apex.home, so your configuration (apex-config.xml as well as your adminlistener/managerlistener credentials and the information where your static contents (images) resides) would have been stored in +/tmp/apex+ as well. Depending on your OS, it's likely that +/tmp+ will be "recycled" upon every reboot, so it's lost by now.
My next guess is that you use some kind of automatic startup with nohup or some similar tool. This doesn't offer the console needed to enter credentials and images location.
You can solve this issue by starting APEX Listener directly, i.e. using a regular terminal instead of some background service, so you'll be able to rerun the initial configuration.
Please note that running APEX Listener in Standalone Mode is not recommended for a production deployment. If you can't do anything about that right now, I'd at least recommend to include apex.home in your startup and let it point to a permanent file system location, e.g.
There is also a parameter apex.images to provide the path to the images instead of using the value from first startup. See the APEX Listener Installation and Developer Guide for details and further options for deploying APEX Listener.
java -Dapex.home=/u01/oracle/product/apex_listener/conf -jar apex.war
Thanks, Udo. What you have pointed to, the location of the config files on the /tmp directory was, for sure, the issue.
I have managed to reconfig the listener and now have it back up again. However, I would like to stop it form using the /tmp directory to prevent this from happening in the future.
I opened the apex.war file and editing the web.xml file such that I uncommented the section, config.dir and changed the value to a permanent location. I restarted apex but, the change doesn't seem to have any affect. That is, it is still using the /tmp/apex directory.
Does your command do the same thing, albeit form the command liine?
Do I have to call it like that everytime or will calling it once like that change the location from that point forward?
the config.dir from web.xml is just for the apex-config.xml , not for user credentials. I'm not sure if it is evaluated at all when running in Standalone Mode, perhaps I'll run a test case to be sure.
Anyway, you need to set that startup parameter, as mentioned before. Obviously, you need to do that upon every startup, as there is no way to know where the home would be without having any configuration data. However, once you've finished the initial configuration, you just need to pass the parameter for the home, you don't need to re-enter the configuration data if that home has been configured before.
Not sure that I understand...it seemed like you were saying that I did need to pass the parameter every time but, then, later you said "you don't need to re-enter the configuration data if that home has been configured before"
Let me ask a more specific question to make sure I am doing this correctly.
Right now, this is the command line with which I start up the stand alone listener: /usr/java/jdk1.6.0_27/bin/java -jar /u01/oracle/product/apex_listener/apex.war
You are saying that I need to use: /usr/java/jdk1.6.0_27/bin/java -Dapex.home=/u01/oracle/product/apex_listener/conf -jar /u01/oracle/product/apex_listener/apex.war
My question is, do I need to pass in the Dapex.home argument only when I initially reconfigure. Or do I need to permanently issue the command with the "Dapex.home" switch included?
Thanks for clarifying,
/usr/java/jdk1.6.0_27/bin/java -Dapex.home=/u01/oracle/product/apex_listener/conf -jar /u01/oracle/product/apex_listener/apex.warRight. You need to pass that parameter every time you start your APEX Listener, because, as I intended to clarify before, the application wouldn't have any chance to know where it's home would be if you didn't pass that parameter.
What I meant to say is that you need to enter the configuration data (images, usernames and passwords) just upon initializing that home directory, i.e. upon the first time you call APEX Listener using that path. Later, you can run APEX Listener in background (referencing a proper home directory).
P.S.: If your question is answered, please mark this thread and any helpful or correct answer accordingly to help other users searching for a similar issue to spot relevant posts easily. Thanks!
Edited by: Udo on 02.04.2012 20:12
All is working as desired now.