8
This number controls the size of the "analysis queue". For example,
if swa.analyzers.count=1 and someone has started an analysis, a second analysis
won't start until the one worker is finished with the first analysis. Users will still be able
to queue new analyses even if all of the analysis workers are busy.
While you are free to change that value to higher ones, please me mindful that it has a
direct impact on both the application and database server performance. As a general
rule, the more powerful the hardware, the more it will be able to process
simultaneously.
2. By default, Code Dx will store the last 5 copies of your analyses per project. To change
that behavior you should change the value of the swa.storage.num-analysis-runs-
to-keep property in the configuration file.
3. For the analyses that are stored, Code Dx will by default maintain a copy of the raw
inputs it received for processing. While these inputs are not used by Code Dx once it
finishes the analysis process, they are kept around for archival. If storage space is an
issue, the swa.storage.keep-raw-inputs can be set to false to prevent Code Dx
from storing the raw inputs.
4. Code Dx bundles various static analyzers that run independently during the analysis
process. Each of these tools requires a memory budget during its own analysis. The
memory requirements vary based on the sizes of the codebases the analyzers are
checking. By default, Code Dx allows each Java-based tool to allocate up to 1GB of
memory using the java.tools.maxmem ory property. This can be changed, however, to
better match your project sizes. CAT.NET is given 2 GB but this can be changed using
cat.net.maxmemory. Ruby-based tools are run via JRuby, and are allowed a default
maximum of 1GB of memory. This can be changed using ruby.tools.maxmemory.
Changing any of the analysis behavior properties can be done at any time after the initial
installation, however, you will still need to restart the server in order to reload the properties.
3.2.8 Active Directory Configuration
Code Dx allows you to create and delete new users that are only known to the Code Dx system.
You may, however, want to let users use the same credentials as they do for your organization.
To facilitate this, you must set up an Actve Directory configuration in the 'props' file. For
example:
shiro.activedirectory.realm =
org.apache.shiro.realm.activedirectory.ActiveDirectoryRealm
shiro.activedirectory.url = ldap://172.17.17.8:389/
shiro.activedirectory.searchbase = dc=avi,dc=com
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern