Very often, I read tips for setting specific options. A good example is this blog entry of Berthold Maier.
And very often, I'm sick of doing this in the JDK files.
Most of the times it means that the whole JDK is configured correctly for one specific application (OC4J in this case) but not for others. Following this path further often leads to many application specific instances of the JDK with the implication that you often don't follow the recommended JDK updates, because you simply forget to do this.
Therefore I really like the alternatives the JDK provides, but many don't care about. For the above example of setting the OC4J specific security values, I recommend to use this JDK command line option:
-Djava.security.properties=$ORACLE_HOME/j2ee/home/config/jazn.security.props
This doesn't restrict your JDK for one, and only one, application and you could keep only one JDK version installed.
Bonus
The above mention jazn.security.props contains the correct settings for OC4J which helps me avoid many typing errors by using this file.
Comments (2)
please, i support what you have presented in blog but am sorry to say i have tried using this in my setting to create an isql*plus admin user but it didnt work out it was giving an error that :
java class not exist.
Posted by BABATUNDE ABIODUN | August 5, 2009 8:29 AM
Posted on August 5, 2009 08:29
For OC4J 10.1.2 and later this option should be -Djava.security.policy=$ORACLE_HOME/j2ee/home/config/java2.policy. On Oracle AS you will find this configured in $ORACLE_HOME/opmn/conf/opmn.xml. For the Oracle DB the file name is similar ($ORACLE_HOME/oc4j/j2ee/home/config/java2.policy).
Posted by Olaf Heimburger | August 17, 2009 1:46 PM
Posted on August 17, 2009 13:46