Configuration File for iobserve

[rju]

the iObserve analysis is a rather complex piece of software utilizing a vast set of simple filters and composite stages. The configuration over command line parameters for all potential combinations is unsatisfying. Therefore, we should switch to a configuration file.

In general the analysis supports X distinct analyzes:

• Behavior analysis
• Deployment and Allocation
• Dataflow and Geolocation
• Separate Geolocation
• Call and Messages Traces

Not all these features are sufficiently implemented. However, they are intended features which should be activated separately. Also for some analyses, there are different strategies and dependencies. for example, the behavior analysis uses a set of different clustering and classification mechanisms.

[rju]

feature model analysis.pdf

[rju]

Each feature comes with a special set of properties. a) activation property (name of composite stage) b) unique configuration parameters for these filters (which does not include all PCM models they have a separate group)

PCM Support is always required and needs therefore no activation. However, it contains a set of model parameters. One for each file: org.iobserve.pcm.support.base=directory org.iobserve.pcm.support.correspondence=correspondence-model-name.ext org.iobserve.pcm.support.repository=repo name in base directory org.iobserve.pcm.support.allocation=allocation repo org.iobserve.pcm.support.resource.environment=resource environment ... org.iobserve.pcm.support.neo4j.path = path to use for the neo4j DB

feature model analysis.pdf

[rju]

Behavior and dataflow require traces.

[rju]

Started with configuration file.

[rju]

Fixed