Solving Operational Business Intelligence with InfoSphere Warehouse Advanced Edition

166 Solving Operational Business Intelligence with InfoSphere Warehouse Advanced Edition

business and provide the means to address those critical questions of where and

how to drive their company.

4.6.1 Installation example of InfoSphere Warehouse Insight Pack

In this section, we examine the process of installing the InfoSphere Warehouse

pack for Customer Insight and investigate the included assets. Because the

same installation process can be utilized for the remaining two Insight packs,

they are not part of this example.

When you install an InfoSphere Warehouse Insight pack, a folder in the local file

system is created into which the assets of the pack are placed. The contents of

this folder are shown in Figure 4-58.

Figure 4-58 Location and assets contained in the IBM InfoSphere Warehouse Customer Insight pack

Investigate each of these folders to see all the assets that are provided. The

Cognos folder contains the compressed files required to import reports into

Cognos and to import the models into Framework Manager. The DDL Script and

Sample Data folders contain the SQL and data to create the sample database.

The Model folder contains the files required to import the data models into

Design Studio. The Docs folder contains documentation about the Customer

Insight pack including the document “IBM InfoSphere Warehouse Pack for

Chapter 4. Data modeling: End to end 167

Customer Insight v8.2.2 Getting Started.pdf.” This document gives step-by-step

instructions for installing the Warehouse Pack.

A default location on a Linux Operating System-based server for installing the

Customer Insight Pack is /opt/IBM/Industry Models.

For our example, we install the models on our Windows client to give our

development tools access to all the models. On our client the package is

installed into C:\Program Files\IBM\Industry Models.

We perform these steps to install Customer Insight Pack:

1. Open IBM InfoSphere Data Architect and create a new project from File 

New and give the project a name, that is Customer_Insights.

2. From the File menu, select Import  General  File System and browse to

the Model directory the installation location of the Insight Pack. Select this

directory as the source.

168 Solving Operational Business Intelligence with InfoSphere Warehouse Advanced Edition

3. On the next panel, select all the required model files from within the source

directory, and set a location within the new project as the target for these files.

See Figure 4-59.

Figure 4-59 Import Model files from IBM InfoSphere Customer Insight Pack into IBM

InfoSphere Data Architect

Chapter 4. Data modeling: End to end 169

4. We can now navigate the models that have been imported and view the

information contained. See Figure 4-60. The complete model is relatively

large but has been broken down into a number of star schemas.

Figure 4-60 Models contained within the InfoSphere Warehouse Customer Insight Pack

5. Figure 4-61 on page 170 shows the same three model files that are loaded

into a project within Design Studio. Note the OLAP cube elements within the

Customer Insights Cube model file.

This model is set up to do two types of customer analysis: Customer Profiling

and Customer Profitability. There are two star schemas for each type. One to

deal with Individual customers and one to deal with organization customers.

So there are a total of four star schemas.

170 Solving Operational Business Intelligence with InfoSphere Warehouse Advanced Edition

There are two diagrams for each star schema: a table view and a column

view.

Figure 4-61 The three model files from the Customer Insight pack loaded into IBM Design Studio

6. Double-click the Individual Customer Loyalty Schema – star schema to

show the table view (Figure 4-62 on page 171). This is a simple star schema

with one fact table and six dimension tables.

Most of the dimensions used for the star schemas are derived from the data

held within the staging tables where data is loaded before any ETL process