Service Virtualization

Hello All,

Could someone help me in finding the difference between local.properties , site.properties and lisa.properties.

I am confusing what to update when , when we want to add properties.

Thanks in advance.

Regards,

Sankar

• Once the software is installed, DO NOT copy previous version local.properties, site.properties, dradis.properties (9.1.0 and later), logging.properties or lisa.properties files to your new install.
  • If you need to change a property to a different value than what is delivered in lisa.properties, update the local.properties or site.properties files. These are delivered as templates, so copy _local.properties to local.properties and _site.properties to site.properties.  The lisa.properties file should never be modified.
  • Properties files are evaluated in the following order:
    • lisa.properties
    • site.properties take precedence over lisa.properties
    • local.properties takes precedence over site.properties and lisa.properties
    • Command line and vmoptions files takes precedence over all properties defined in any of the properties files.

Note: dradis.properties is only used when configuring the Enterprise Dashboard to use an external database.

Tech Tips: Best Practices Installing and Verifying DevTest Out of the Box 

Thanks Marcy.

Its a useful info.

The location and order they are read is very important.

The lisa.properties is read 1st, this is delivered with the larger set of properties provided at the product level.  This is installed with the product in the local file system.

The site.properties is read second, this means it can override or replace property key=value pairs.  This is only read at the registry level and when workstation, coordinator, simulator, registry, broker, portal connect to the registry they are passed down when the connection is established.  This is why you place the database connection information into the site.properties, it is automatically distributed to all other processes on connection.

Then the local.properties is read from the local machine and can override properties previously set or new ones can be set.  These are more personal settings at the workstation, coordinator, simulator,, broker, portal level.

When you set properties at command line via -j-d they cannot be overridden by a latter name=value pair, they are special and always maintained.