Content Pack Structure
Generally speaking, two content pack (.cp) folders are needed under the <VDW_HOME>/Content
directory for a single task:
CUSTOMIZATION_PPM.cp
: Contains JSON files that define source entities, extraction entities, and stream entities.CUSTOMIZATION_TARGET.cp
: Contains JSON files that define target entities.
Note: When deploying content packs, you always need to deploy CUSTOMIZATION_TARGET.cp
first. Otherwise, you may not be able to deploy CUSTOMIZATION_PPM.cp
and process the rest of tasks.
The folder structure of the content packs is shown as follows:
-
CUSTOMIZATION_PPM.cp (root folder)
-
dwmetadata (folder)
-
entities (folder)
- Source entity JSON (file)
-
streams (folder)
- Stream entity JSON (file)
-
-
extmetadata (folder)
- Extractor entity JSON (file)
- cp.json (file)
-
-
CUSTOMIZATION_TARGET.cp (root folder)
-
dwmetadata (folder)
-
entities (folder)
- Target entity JSON (file)
-
- cp.json (file)
-
The following table describes the JSON files.
JSON file |
Description |
---|---|
Target entity JSON |
Stores information related to the target table, such as field names and relation information with other tables. |
Source entity JSON |
Stores information related to the source table such as field names and incremental extraction information. |
Stream entity JSON |
Stores information related to the stream, such as the source entity, target entity, and SSI transforming SQLs. |
Extractor entity JSON |
Stores information related to data extraction, such as SQLs for extracting data. |
CP JSON | Stores information related to content packs, such as target entities and source entities. This file is the entrance for the corresponding content pack. |