The OOTB product will come pre-configured with an evidence.properties file - see Step 2: Create and Configure Evidence Properties File for details. For the purposes of overriding an OOTB product, the custom product will require its own, thin version of evidence.properties.
The crucial property here is 'override.product'. If this is not set, the evidence generator will assume that this evidence product is brand new. If it is set, it must be set to the 'product.name' of an existing evidence generation product. All the other properties have already been defined in Cúram Evidence Generator Specification - Appendix A evidence.properties .
# Unique name (product.name) of the OOTB product to override override.product=SampleEGProduct # Prefix used to specify where all metadata files are copied to product.prefix=SEG # Other Mandatory Properties in an Overriding Product product.build.option=true evidence.properties.dir = %SERVER_DIR%/components/custom/EvGenComponents/SEG/evidence properties.home=${evidence.properties.dir}/properties/ server.metadata=${evidence.properties.dir}/server/metadata caseType.integratedCase.metadata = ${evidence.properties.dir}/integrated/metadata caseType.product.metadata = ${evidence.properties.dir}/product/metadata
EJBServer/components/custom
As the custom directory may eventually contain many of these overridden products (and evidence directories), it is recommended that some sort of naming scheme be devised. e.g.
EJBServer/components/custom /EvGenComponents/<ProductName>/evidence