Text of Internal and Confidential COGNOS Decision Stream Cognos CoE
Internal and Confidential COGNOS Decision Stream Cognos CoE
11 September 2015 Agenda Getting Started Components of DecisionStream Definitions DecisionStream Catalog Database Connections Fact Builds Dimension Builds JobStreams SQLTXT Designer SQL Term Command Line Interface
11 September 2015 Modules 9. Definitions 1. Getting Started 2. Create a Catalog5. Dimension Builds 6. Job streams 7. SQL Text Designer 8. Command Line Interface 3. Fact builds 4. Data Delivery Modules
11 September 2015 Module 1 Getting Started
11 September 2015 The primary purpose of DecisionStream is to create integrated data marts by: extracting operational data from multiple sources merging and transforming the data to facilitate reporting and analysis delivering transformed data into coordinated data marts What is DecisionStream?
11 September 2015 The Purpose of DecisionStream Transformations OLTP - x/y + Data Integrated Data Marts
11 September 2015 Decision Stream Architecture Design Client APIScripts Platforms Windows NT,95,98, 2000 Desktop DecisionStream Process Metadata Operational Sources DB2 Oracle SQL Server Informix ODBC Sybase Text MetaData Targets Impromptu Transformer Architect Microsoft SSAS Essbase Server Engine NT or UNIX Server HPUX AIX Solaris IBM AIX 4.2 COMPAQ TRU64 DECISIONSTREAM Custom DBMS Files Flat Files ERP
11 September 2015 3 How DecisionStream Creates Data Marts Dimension Delivery 5b. 4 Sales 1 Dimensional Framework ProductTimeLocation Dim Data Sources 2 Data Source Data Source DataStream DataStream MetaData Delivery 5c. 5a. Fact Delivery
11 September 2015 DecisionStream Interface
11 September 2015 Interface Objects The core elements in a DecisionStream catalog are: Builds DataStreams Transformation Models Delivery Modules
11 September 2015 Interface Objects (Contd) The core elements in a DecisionStream catalog are: JobStreams Dimensions Hierarchies and Lookups Templates Connections Functions
11 September 2015 DecisionStream Tools
11 September 2015 Module 2 Create a Catalog
11 September 2015 What is a Catalog? A catalog is a container for DecisionStream metadata.
11 September 2015 A DecisionStream Catalog provides a central repository for the information that defines how DecisionStream extracts, transforms, and delivers data. You can store a DecisionStream Catalog in either a dedicated database or a database that you use for other purposes, such as a target data mart. A Catalog consists of a set of data tables that can reside in any database for which DecisionStream has create permissions. You can create only one Catalog per database. DecisionStream Catalog
11 September 2015 Diagram illustrates How DecisionStream extracts and transforms data from the data sources and how it delivers data to the target marts The flow of data from the data sources to the target data marts DecisionStream Catalog
11 September 2015 Shared Items in a Catalog Library items can be used throughout the catalog in a variety of different builds and JobStreams. A catalog library consists of: Dimensions Connections Functions
11 September 2015 Create a Catalog You can create a Catalog in the DS_New sample database. Steps 1. From the File menu, click New Catalog. If you are prompted to disconnect from the current Catalog, click OK. The New Catalog dialog box appears. 2. In the Name box, type MyCatalog and then click Next. 3. In the left pane, click ODBC. 4. In the Data Source Name box, click DS_New. 5. Click Finish. DecisionStream creates the Catalog tables and opens the new Catalog. 6. From the File menu, click Save Catalog. DecisionStream Catalog
11 September 2015 Backup and Restoration of a Catalog Backup files are useful for recovery and emergency situations. Write the catalog tables to an ASCII text file for later recovery.
11 September 2015 Creating an ODBC Connection Steps to define connections to ODBC databases set up for the Great Outdoors Company. Steps 1. Open the MyCatalog catalog that you created in Chapter 2. 2. In the Library, right-click Connections, then click Insert Connection. 3. In the Alias box, type GO_Sales 4. Click the Connection Details tab. 5. In the left pane, click ODBC. 6. In the Data Source Name box, click GOScer3. 7. Click OK to close the Connection Properties dialog box. Database Connections
11 September 2015 Creating a connection to SQLTXT Database Steps 1. In the Library, click the Connections folder. 2. From the Insert menu, click Library, and then click Connection. 3. In the Alias box, type DS_Sources 4. Click the Connection Details tab. 5. In the left pane, click SQLTXT. 6. In the Definition File box, click Browse, then select the DS_Sources.def file in the Cognos samples directory. 8. Click OK to close the Connection Properties dialog box. Database Connections
11 September 2015 Creating a connection to Oracle Database Steps 1. In the Library, click the Connections folder. 2. From the Insert menu, click Library, and then click Connection. 3. In the Alias box, type DS_OracleSrc 4. Click the Connection Details tab. 5. In the left pane, click Oracle SQL*Net. 6. Enter the values for User Name, Password and SQL*Net Service. 8. Click OK to close the Connection Properties dialog box. Database Connections
11 September 2015 Module 3 Fact Builds
11 September 2015 A DecisionStream fact build specifies how to extract, transform, and deliver data. Data may come from multiple data sources, Each of which has its own naming and storage conventions. A fact build can acquire data from one or more data sources merge and clean the source data aggregate the data with reference to the dimensional framework deliver the fact and dimension data to one or more data marts deliver metadata to OLAP systems and Cognos BI applications Fact Builds
11 September 2015 Deliver 10100101 The Fact Build Process Transaction Data Sources Structure Data Sources AcquireStar Join Merge Transform Aggregate Partition Filter Dimensional Framework
11 September 2015 Fact Build Data Elements Dimension Measure Attribute Derivation A dimension key or data that is used to qualify a measure. Quantitative data or values that can be aggregated. These are usually Key Performance Indicators (KPIs). Additional information that is not a dimension element or measure but that may be of interest. A calculation or transformation.
11 September 2015 Fact Build Wizard The Fact Build Wizard guides you step-by-step through the process of creating a new fact build.
11 September 2015 Types of Fact Builds Fact build types provide default settings for the delivery of data marts.
11 September 2015 The Fact Build Wizard: Add a Data Source A data source for the fact build is chosen from the available connections. This source contains the transactional data to be transformed.
11 September 2015 The Fact Build Wizard: Create the SQL Data Source Tables and columns to be read from SQL statement created
11 September 2015 The Fact Build Wizard: Map to Fact Build Elements Elements of the Transformation Model Columns returned from source data by SQL
11 September 2015 The Fact Build Wizard: Modify Attributes The elements of the Transformation Model are created automatically by the Fact Build Wizard but may need to be modified. Elements of the Transformation Model Click here to modify the types of elements
11 September 2015 The Fact Build Wizard: Link to the Dimensional Framework Dimension elements are related to reference structures.
11 September 2015 The Fact Build Wizard: Fact Data Delivery
11 September 2015 Fact Build Visualization Dimensions associated with the build Fact and Dimension tables Metadata delivery to Impromptu, PowerPlay, and Architect Transactional data sources
11 September 2015 DataStream Mapping Visualization You can visualize the mapping of the SQL columns to the build elements by clicking the DataStream tab.
11 September 2015 Transformation Model Visualization Use the Transformation Model tab to view the linkage of the dimension elements to the Dimensional Framework. Mapped Reference Structures
11 September 2015 Fact Delivery Visualization By clicking the Fact Delivery tab, you can view the mapping of the elements to the target fact table.
11 September 2015 Delivery Modules The three delivery module types are: fact dimension metadata