Administer > Administer ITBA > Content Administrator > Data Management - Install Content Pack

Data Management - Install Content Pack

A Content Pack is a set a files that defines the execution of an ETL along with all its parameters.

The Content Pack Manager page enables you to install or upgrade Content Packs.

ClosedTo access:

Select ADMIN > Data Management >  Install Content Pack.

ClosedContent Packs

Content packs include:

  • The definition of the data model used for the connection.

  • The type of data gathered from the data source.

  • The ETL definitions.

  • The definition files.

  • The configuration files.

  • The scripts that help build and define the Data Warehouse.

The Data Warehouse can connect to other products (data sources) and gather data about these products. An integration is available for each product (data source).

The connection from the data source to the DWH is called an integration content pack (iCP). A Content Pack is a set a files which defines the execution of an ETL along with all its parameters. Each content pack uses an extractor in order to extract the data from the specific data source and contains all the artifacts needed to connect to the relevant data source and to gather data from that data source.

The mapping between the raw data from the data source and the target database in the Data Warehouse is included in the ETL. Business Analytics runs the KPI engine that reads the data from the target database, creates the relevant KPIs from that data, calculates the value, and status of the KPI and displays the relevant information in the Dashboard.

The structure is as follows:

├──CORE Includes ETL artifacts for data consolidation and data model for integration and target layer.
│ ├──cp_manifest.properties Includes CP name, CP type, CP version, dependency version (platform version, Core version, data source types, extractor class name, extractor library paths).
│ ├──dw_app.properties includes the name of the relevant Content Pack.
│ ├──dw_app.xml legacy file.
│ ├──INBUILT Includes all out of box content artifacts.
├──<iCP> Out of the box content packs for the integration with CSA, PPM, or SM
│ ├──CONF  
│ ├──cp_manifest.properties Includes CP name, CP type, CP version, dependency version (platform version, Core version, data source types, extractor class name, extractor library paths).
│ ├──dw_app.properties  
│ ├──dw_app.xml  
│ ├──EXTERNAL Includes External file (optional). Not for SM.
│ ├──EXTRACTOR Includes the CP Extractor (optional).
│ ├──INBUILT Includes all out of box content artifacts.
├──DEMO_CONTENT  
│ ├──cp_manifest.properties Includes CP name, CP type, CP version, dependency version (platform version, Core version, data source types, extractor class name, extractor library paths).
│ ├──dw_app.properties  
│ ├──dw_app.xml  
│ ├──INBUILT Includes all out of box content artifacts.
├──KPILIB  
│ ├──cp_manifest.properties Includes CP name, CP type, CP version, dependency version (platform version, Core version, data source types, extractor class name, extractor library paths).
│ ├──dw_app.properties  
│ ├──dw_app.xml  
│ ├──INBUILT Includes all out of box content artifacts.
│ ├──README.md  

You must run the Connect Data Source wizard to configure and activate the content packs, depending on the products you want to integrate with.

If you have created a Content Pack using IDE, make sure to add it to the $HPBA_HOME/ContentPacks directory. Content Packs located in the directory appear in the Content Pack Management page where you can install or upgrade them. For details on IDE, see Content Extension

The out-of-the-box content packs are:

  • CORE content pack. This is the central content pack that is automatically installed during the post-installation process. It takes consolidated data to the target schema. It includes all the dimensions, and entities of the Data Warehouse. It also provides the organization of definitions and hierarchies. All the other integrations depend on the CORE content pack.

  • Specific Content Packs. Each integration with a data source has its dedicated Content Pack. For details, see KPIs, Metrics, Contexts, and Data Source Integrations.

Context

A context is the result of a semantic layer of metadata that creates a business oriented view of the data. The context contains a schema of the tables that make up the dimension and measurement objects. The context is an interface between the data warehouse and the analytics that display the data. It then corresponds to the business contexts used in ITBA.

ClosedExtractors

The supported extractors for the OOTB Content Packs are as follows:

Content Pack Extractor Type
PPM(Oracle) DB
SM(MSSQL, Oracle, DB2) DB
ALM REST API
CSA REST API
AWS SDK
AWSCW SDK
AM DB
SA DB
VPV "REST API"
AZURE "REST API"

ClosedMultiple Integration Content Pack Instances

Multiple Integration Content Packs (M-iCP) provide multiple instances of the same data source or product type. This allows for data source configuration per instance, as opposed to a single activation for the data source. Each instance has its own version and product type. The M-iCP source extraction is based on the DCS extractor technology, and consolidation is enabled between instances.

You can add an instance using the Connect Data Source page. For details, see Data Management - Connect the Data Sources.

ClosedInstall a Content Pack

To install a Content Pack:

  1. Select ADMIN> Data Management >  Install Content Pack.

  2. Click Install for the relevant Content Pack.

    The status is changed to Upgrade and the date of the installation is set in the Update Date column.

ClosedUpgrade an installed Content Pack

To upgrade a Content Pack:

  1. Select ADMIN > Data Management >  Install Content Pack.

  2. Click Upgrade for the relevant Content Pack.

    The status is changed to Upgrade and the date of the installation is set in the Update Date column.

ClosedUninstall a Content Pack

To uninstall a Content Pack, use the ETL Toolkit. For details, see Uninstall a Content Pack.

ClosedContent Pack Manager Page

This page enables you to install or upgrade Content Packs.

User interface elements are described below (when relevant, unlabeled elements are shown in angle brackets):

UI Element

 Description
Content Pack Name

The name of the Content Pack that corresponds to a specific data source.

  • CORE content pack. This is the central content pack that is automatically installed during the post-installation process. It takes consolidated data to the target schema. It includes all the dimensions, and entities of the Data Warehouse. It also provides the organization of definitions and hierarchies. All the other integrations depend on the CORE content pack.

  • Specific Content Packs. Each integration with a data source has its dedicated Content Pack. For details, see KPIs, Metrics, Contexts, and Data Source Integrations.

If you have created a Content Pack using IDE, make sure to add it to the $HPBA_HOME/ContentPacks directory. Content Packs located in the directory appear in the Content Pack Management page where you can install or upgrade them. For details on IDE, see .
Status
  • Installed. The Content Pack has been installed.
  • Not installed. The Content pack has not yet been installed.
  • Processing. The Content Pack is in the process of being installed.
  • Error. A problem occurred when you installed the Content Pack.
Content Pack Version

The version of the Content Pack.
Operation Date

The date when the Content Pack was last installed.
<Action>

Install. Click to install.

Upgrade. Click to upgrade.

Send Help Center feedback