This mighty beasts are quite cool once they get running ... some are more mighty than others, I know!
Listing the ports being used
To get a list of all ports and processes running in the OAS, do
./opmn/bin/opmnctl status -l
Accessing the appserver directly
The OC4J instances do not have an HTTP connector per default. This means that out of the box, the only way to access your webapp is through Apache (what Oracle has branded "Oracle HTTP Server"). This is in production fine, but when testing the appserver itself, you want to access it directly, as you would access your Tomcat or Resin appserver.
Look for an
it should be there. Add a line to its configuration for
your webapp (you'll find the same line in yourdefault-web-site.xml```.
<web-app application="default" name="mywebapp" root="/mywebapp" access-log="false" />
Then add a line like this in you
To enable rotating logs in OC4J, do the following: change
log element to use the odl logger instead
of the file logger. The ODL can, among other things, rotate
the logs. When going through the conifg files you will see
either an access-log element or a log
If you find an
access-log element, comment it
out and replace it with
Likewise, if you find a
element as a
child of thelog
element, replace it withodl```. For example:
Files you need to edit
Updating the configuration
After updating configuration, run the distributed configuration manager and then restart the OC4J instanse you have configured.
Restarting the entire server
$ORACLE_HOME/opmn/bin/opmnctl stopall $ORACLE_HOME/opmn/bin/opmnctl startall
Please note, that usually it is enough to isseu: