Extracted artefacts

Codetables are extracted and saved in files with ctx extensions.

The files are written into a folder located in the destination component (see codetableDir input parameter). Each codetable is extracted into a separate file. Two codetables are extracted:

• EvidenceType
• TemporalEvTypeApproval

Entities (Database Tables):

Entities are extracted and saved in files with dmx extension. There is one such file per entity. These files are written to the data manager folder located in the destination component (see datamanagerDir and dmxDir input parameters). Blob and clob records are extracted into external files and referenced from DMX files. Blob and clob files are saved into separate folders (named blob and clob) located inside the dmxDir folder.

• EvidenceTypeDef: this entity stores the Dynamic Evidence Types on the system and it is the first to be extracted. The Evidence Type extraction strategies mentioned earlier determine what records to extract from this entity. If no records can be extracted from EvidenceTypeDef the extraction process terminates.
• EvidenceTypeVersionDef: extraction of this entity is dependent on EvidenceTypeDef. It stores multiple metadata Versions for Dynamic Evidence Types. Active and In Edit Versions are extracted for each extracted record (Evidence Type) from EvidenceTypeDef.
• EvidenceTypeDefinition: maps an Evidence Type to an Evidence Nature. Extraction is dependent on EvidenceTypeDef entity.
• SecurityGroup: contains security group definitions on the system. There is an auto generated Security Group for each active Dynamic Evidence type, hence this entity is dependent on EvidenceTypeDef in the extraction process. Users have access to Security Groups via the System Administration application. If auto-generated Dynamic Evidence Security groups are modified or deleted they will not be picked up by the extractor. Additionally, Security Identifiers and Security Group SID mappings will not be extracted for modified groups.
• SecurityIdentifier: this entity depends on SecurityGroup and SecurityGroupSid in the extraction process. Only Security Identifiers linked to extracted security groups are extracted.
• SecurityGroupSid: links Security Identifiers to Security Groups. If any of the extracted Security Identifiers are linked to the EVIDENCEGROUP security group, these links are also extracted.
• AppResource: this entity stores miscellaneous information in blob fields. It depends on EvidenceTypeDef and EvidenceTypeVersionDef in the extraction process. The following artefacts are extracted:
  • Evidence Type localizable descriptions: extracted as properties files in the blob folder, one per Dynamic Evidence Type.
  • Evidence Type Version localizable properties: extracted as properties files in the blob folder, one per Active Evidence Type Version.
  • Tab configuration files: extracted as XML files in the blob folder. Up to three files are extracted per Active Evidence Type Version (tab, menu, navigation configuration files).
  • The previously used single evidence descriptions properties resource (DynEvd_EvidenceTypeDescriptions.properties), if found, is split into individual (one per Evidence Type) properties files and stored in the blob folder.
• CreoleRuleset: this entity stores published rulesets and it is dependent on EvidenceTypeDef and EvidenceTypeVersionDef entities. Data and processing rulesets are determined from extracted EvidenceTypeDef records, while custom defined rulesets (calculated attributes, validation and summary information) are determined from extracted active EvidenceTypeVersionDef records.
• CreoleRulesetEditAction: stores In Edit rulesets and has dependency on EvidenceTypeDef and EvidenceTypeVersionDef entities. Data and processing rulesets are determined from extracted EvidenceTypeDef records, while custom defined rulesets are determined from extracted In Edit EvidenceTypeVersionDef records.
• CreoleRulesetCategoryLink: links rulesets to categories. It is dependent on both CreoleRuleset and CreouleRulesetEditAction in the extraction process
• EvidenceRulesetDef: this entity maps an Evidence Type to In Edit data and processing rulesets and to a Rule Object Propagator Configuration.
• RuleObjectPropagatorConfig: stores Propagator configurations, one for each Active Dynamic Evidence Type. EvidenceRulesetDef links this entity to Dynamic Evidence Types (EvidenceTypeDef).
• LocalizableText: this entity links Propagator configurations to their localizable descriptions. It has a dependency on RuleObjectPropagatorConfig for extraction.
• TextTranslation: stores Propagator configuration descriptions and depends on LocalizableText entity for extraction.
• ProductEvidenceTypeDefLink: this entity links Dynamic Evidence Types to Products and it is optionally extracted. It depends on EvidenceTypeDef entity in the extraction process.
• AdminICEvidenceTypeDefLink: this entity links Dynamic Evidence Types to Integrated Cases and it is optionally extracted. It depends on EvidenceTypeDef entity in the extraction process.
• CaseConfigEvidenceLink: this entity links Dynamic Evidence Types to Application Cases and it is optionally extracted. It depends on EvidenceTypeDef entity in the extraction process.
• KeyServer: only a single record is extracted from this entity. This is the key set (DYNEVDCODE) used to generate Dynamic Evidence Type codes.

Section Configuration Files:

Section configurations are stored in the AppResource entity. Each section configuration may refer to multiple components which makes extraction via DMX files impossible. Instead, section configurations are extracted into section contribution files (with extension sec) and saved in the tab folder (see tabDir input parameter).