Step 3 Extract Evidence

When all Dynamic Evidence Types have been defined, most customers will at this stage want to preserve the state of these Dynamic Evidence Types in their Software Configuration Management system. The Dynamic Evidence Extractor provides this functionality (see Dynamic Evidence Configuration Extractor for more details).

Note: That it is not a completely mandatory requirement – it is possible to create Dynamic Evidence Types in a Testing or Staging environment and transport them into a production environment without this step – but for the majority of customers, this will be required.

If a customer does extract their Dynamic Evidence Types, they have to manage the database primary keys and use keys from designated key ranges. If not configured, the data base will just create arbitrary Primary Keys which could result in Primary Key conflicts.

The recommended approach to manage PKs for Dynamic Evidence is to use the Range Aware Key Server (RAKS). This mechanism was developed to support Cúram Configuration Transport Manager and is documented in the Cúram Business Object Module Development Guide. It involves enabling all entities being extracted by the extractor to use RAKS and administration configuration of the RAK server. The benefit of RAKS is that once the system is configured it is guaranteed to generate the correct PKs for newly created records. Dynamic Evidence Type artifacts can safely be extracted as is, without the risk of Primary Key conflicts.