Page History

...

serviceaccount/parasoft-account created
role.rbac.authorization.k8s.io/parasoft-read created
rolebinding.rbac.authorization.k8s.io/parasoft-read-bind created

The following yaml below creates the SOAVirt server. If a custom Persistent Volume Claim name was used in previous steps, make sure to update the 'claimName' field to match the custom name.the custom name.

Required Settings for a Stable Machine ID

Anchor
RequiredSettingsForStableMachineID RequiredSettingsForStableMachineID

As you modify the soavirt-pod.yaml sample shown below or craft your own yaml, be aware that the following fields need to be consistent across upgrades and redeployments in order to assure a stable machine ID:

• metadata: name
• metadata: namespace
• containers: name

In addition, the following environment variables are required:

• env: name: PARASOFT_POD_NAME
• env: name: PARASOFT_POD_NAMESPACE

Note: kind: Deployment is not supported. Use either kind: Pod or kind: StatefulSet.

...

/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 modified copy of your java.security file and save , store it in your parasoft directory (for example, in a ConfigMap, and mount it into the pod at /usr/local/parasoft/) and make your modifications to that file, then add it to your configuration mapjava.security.

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

...