Package Naming Convention
Summary
| Package Type | Pattern | Example |
|---|
| Extractor Code | s4q-extractor-[name]-[version].jar | s4q-extractor-jira-1.0.jar |
| Extraction Configuration | s4q-extractor-[name]-[version].zip | s4q-extractor-polarion-1.0.zip |
| Data Interface | s4q-di-[name]-[version].zip | s4q-di-requirements-1.0.zip |
| KPI Document - KPI Model | s4q-kpimodel-[name]-[version].zip * | s4q-kpimodel-cmmi-1.0.zip |
(*) The usage of
dot,
dash or
underscore depends on the SpagoBI version. It's not possible to rename the package after it has been created!
It can be useful to group all the code developed to extract data from a Tool in one single jar package. To ease the management of these kind of packages include in its name the name of the Tool and the version of the extractor.
s4q-extractors-[name]-[version].jar
Do not forget to provide the installation guide along with the dependencies (jars, xmls, ...).
Group in a single package all the operations that belong to a specific Tool or are dedicated to a specific entity to extract.
s4q-extractor-[name]-[version].zip
Data Interface
Export of an Extraction Operation that uses the Data Interface. For export purpose it's possible to associate a FAKE_DS to complete the operation configuration.
s4q-di-[name]-[version].zip
KPI Document - KPI Model
Create one package for one KPI Document to better handle the different versions and create a modular analytical environment. Provide the right package name during the export steps and
don't rename it later.
s4q-kpimodel-[name]-[version].zip
