Page History

...

/usr/local/parasoft/soavirt/logs
/usr/local/parasoft/soavirt/temp
/usr/local/parasoft/soavirt/webapps/ROOT/WEB-INF/configs/builtin
/usr/local/parasoft/soavirt/webapps/ROOT/felix-cache
/usr/local/parasoft/soavirt/webapps/ROOT/apifiles
/usr/local/parasoft/soavirt/work/Catalina/localhost/ROOT
/usr/local/tomcat/logs/ 

Modifying the java.security File (Optional)

You may want to use a modified java.security file if, for example, you want to enable or disable an specific SSL cipher suite or something similarsuites or make other related security configurations. To do so, create a copy of your java.security file and save it in your parasoft directory (for example, in /usr/local/parasoft/) and make your modifications to that file. Remember to , then add it to your configuration map.

There are a few options you will want to keep in mind when employing applying your changes:

1. When using your modified java.security settings, it's important to disable the global properties. If you don't, they will override your modifications:
   -Djava.security.disableSystemPropertiesFile=true
2. When overriding To override the default security file, explicitly specify that the security properties JVM should use your modified custom security properties file explicitly:
   -Djava.security.properties==/usr/local/parasoft/java.security
Note the double equal sign (==) that tells Java to entirely fully replace the java.security settings that would normally be loaded from the jvm.
3. To enable debugging of what debug which java.security properties were loaded, add the java.security.debug property:
   -Djava.security.debug=properties

Put all together, you would run add the following to the env: section of the soavirt container:

--env        - name: JAVA_OPTS=
          value: "-Djava.security.disableSystemPropertiesFile=true
                       -Djava.security.properties==/usr/local/parasoft/java.security
                       -Djava.security.debug=properties"

...