Setting up XRadar Dynamics

Setup

If you want to run XRadar dynamics, you must have run XRadar statics on at least two versions of the system.

Update dynamics.properties

$YOUR_PROJECT/etc/dynamics.properties includes the default setup for the analysis of one system build with the XRadar. In addition, will the version-specific property files contain information that normally varies for each version. the setup page.

Note that the version-specific property files are shared for statics and dynamics reports. Follow these guidelines when entering dynamics-related data in the version-specific property files (e.g. $YOUR_PROJECT/etc/release1.0.properties, etc):

System Property Description Required
sequence.id the sequence id of this version [1,2,3,4,5,6,etc] for dynamics
days.since.last.release the number of days since previous release for dynamics
[any property in dynamics.properties] overrides the property value specified in dynamics.properties no

Follow these guidelines when entering your data in dynamics.properties:

System Property Description Required
docs.home the directory root to create dynamics report Yes
statics.report=true uncomment if you have a XRadar statics report and want to be able to navigate to statics directly from dynamics. (See also corresponding dynamics.report=true in statics.properties) No
statics.root The root of the XRadar statics docs root (is only valid if statics.report=true) No
dynamics.master.final the final dynamics master report xml file Yes
dynamics.master.base location of the dynamics-master-base.xml file, default value ${xradar.home}/etc/config/dynamics/dynamics-master-base.xml is usually sufficient Yes
dynamics.master.latest.in temporary file containing the latest in-file (necessary for the dynamics_current ant target) Yes
input.doc temporary file, used for merging each statics report into a final dynamics master report Yes
output.doc temporary file, used for merging each statics report into a final dynamics master report Yes

Update $XRADAR_HOME/$YOUR_PROJECT/build.xml

dynamics_merge_history task with one entry for all historic releases. As default, the file is set up with only one release.

Run ant dynamics_all

This task is dependent on having run a statics on all previous releases to be integrated.