CO G NO S

BI

M ET ADA TA

M O D EL ING

PA RT

Demo 1
Identify Components and Reporting Objects in Framework Manager

IN TRO DUCTIO N

T O

FRA M E WO RK

M A NAG ER

Demo 1: Identify Components and Reporting Objects in Framework Manager

Purpose: As the Data Modelers for The Great Outdoors Company, we have been tasked with developing a model that supports the business requirements of our report and ad hoc query authors working with Cognos 8. Before we begin the modeling process, we will become familiar with the Framework Manger user interface to facilitate the modeling process. We will then examine a variety of models to understand how they appear in this interface. Task 1. Open a project that has been modeled relationally and which is based on a relational data source. 1. From the Start menu, point to All Programs, Cognos 8, and then click Framework Manager. The Welcome page of Framework Manager appears. From here, you can create projects, navigate to and open existing projects, or open a project that has been recently opened. 2. Under Projects, click Open a project, and then in the Open Project dialog box, navigate to C:\Program Files\cognos\c8\ webcontent\samples\Models\gosales_goretailers. 3. Click gosales_goretailers.cpf, and then click Open. The Log on page appears.
Instructional Tips If necessary, maximize the Framework Manager Welcome window.

CO G NO S

BI

M ET ADA TA

M O D EL ING

PA RT

4. In the User ID box, type admin, in the Password box, type Education1!, and then click OK. The Framework Manager user interface appears as shown below.

Task 2. Examine objects in the Project Viewer. 1. In the Project Viewer pane, expand the gosales_goretailers namespace . The Project Viewer appears as shown below:

Instructional Tips If necessary at this point, the instructor can discuss the structure of this model. A two-layer structure is used, with objects representing the data sources contained within the Database view namespace and objects representing the business view of the data source objects contained outside this namespace (at the root of the gosales_goretailers namespace). This layer is also referred to as the Business view, because it is these objects that are typically published and made available to report authors. This view can also be contained within a separate namespace or folder, typically named Business view.

The model consists of a root namespace, with other all other objects appearing within this namespace. At this level, the root namespace contains query subjects, a folder, and a namespace. From the icons, we can see that some of the query subjects contain query items of type Fact , while others do not .

IN TRO DUCTIO N

T O

FRA M E WO RK

M A NAG ER

2. Expand the Orders query subject

The Project Viewer now appears as shown below:

Additional Information The root namespace cannot be deleted. Use the Properties pane to view and modify the properties of the objects you last selected in either the Explorer View, Diagram View, Project Viewer, or Search pane. Although the icon is not shown in the demo, you may also see query items of type Identifier .

At the level that is now shown, this query subject contains query items and a folder. Some query items have their usage property set to Attribute , while others have it set to Fact . 3. Expand the Filters folder. This model includes some stand-alone filters that, when published as part of a package, can be used by report authors to filter their reports. 4. Expand the Data Sources folder.

This folder contains the two data sources currently referenced in this model. For this model, these data sources are based on relational databases. Data sources are specified during the import of metadata. 5. Expand the Parameter Maps folder.

Additional Information A filter can be added as a model object or it can be embedded within a query subject definition. The latter can be done through the user interface or the query subject s SQL can be manually edited. Filters created in Framework Manager are discussed in the module titled Prepare Metadata in Framework Manager . If there are query subjects that reference a data source in a model, then the data source cannot be deleted from the model. Instructional Tips The use of parameter maps, session parameters, and macros is discussed in the module titled Create a Project and Prepare Metadata .

This folder contains a three parameter maps . You can use a parameter map in combination with a session parameter to create a macro that lets you model a single query subject to represent all possible data source languages. 6. Expand the Packages folder.

This folder contains a package that is available for publishing to the Cognos 8 server. A package contains all or a subset of the metadata from the model.

CO G NO S

BI

M ET ADA TA

M O D EL ING

PA RT

Task 3. Examine different views of the user interface. 1. In the Project Info view, click Explorer. The Explorer appears as shown below:

Additional Information By default, the Project Info view is found in the middle of the user interface between the Project Viewer and the Summary panes.

This view provides a flat view of the contents of the project, as opposed to the hierarchical view objects provided by the Project Viewer. 2. On the toolbar, click Back to return to the Project Info view, and then, in the Project Info view, click Diagram. This view shows the hierarchical view of the objects in the project in a diagram. In this view, we can access, modify, and create objects. 3. Scroll down in the Diagram view to locate the Database view namespace. 4. Expand the Database view namespace and the GO Sales folder. 5. From the View menu, point to Views, and then if necessary click Diagram. The Diagram appears as shown below:
Instructional Tips You may have to reposition the diagram using the scroll bars and resizing handles to get this exact view. The point is to show how the Diagram can be used to access and modify relationships.

This view of the diagram shows the relationships among objects, in this case the query subjects in the GO Sales folder. This is a relational model. From the Diagram view, we can access, modify, and create relationships. 6. Resize the left, right, and bottom borders of the Object Diagram so that it fills the screen. 7. From the toolbar, click the Diagram Sizing list click Fit All. , and then

All the objects and relationships in the model are now visible. 8. Click the Diagram Sizing list, click 75%, and then resize the diagram to approximately its original view, so that the other panes are again visible. 9. In the Project Viewer pane, expand the Database view namespace and the GO Sales folder, right-click the Order details query subject, and then click Locate in Diagram. The Diagram is repositioned to focus and highlight the Order details query subject. The following buttons the layout, and set the focal point. can be used to zoom, set

10. In the bottom right corner of the diagram, click and hold on Overview . A smaller scale diagram of all the objects and relationships appears. This provides perspective on where the current focus of the larger diagram is, in relation to other objects and relationships. 11. Right-click on any white portion of the Diagram, point to Current View, and then click Large Icons. The query subjects now appear with the same icons as seen in the Project Viewer. 12. In the Project Viewer pane, under Database View expand the Retailers namespace. 13. Right-click the Contact query subject, and then click Locate in Diagram. In the Diagram the Contact query subject is highlighted. 14. In the Diagram, click the Contact query subject, and then from the toolbar, click Set Focal Point . The diagram is redrawn so that object relationships appear to be originating from the Contact query subject.

CO G NO S

BI

M ET ADA TA

M O D EL ING

PA RT

Task 4. Launch and examine the Context Explorer. 1. In the Project Viewer pane, under the GO Sales folder, right-click Order details, and then click Launch Context Explorer. The Context Explorer window appears. We can see all query subjects that the Order details query subject is directly related to as well as the cardinalities of those relationships. 2. Right-click the Product query subject, and then click Show Related Objects. Product receives the focus and we can see all the query subjects Product is directly related to. 3. Right-click the Order header query subject, and then click Show Related Objects. Order header receives the focus and we can now see all the query subjects Order header is directly related to as well as maintaining the query subjects that are related to Product as shown below:

4. Close the Context Explorer. Task 5. Search for objects. 1. On the Tools pane, click the Search tab. The Search pane replaces the Summary pane in the user interface, and appears as shown below: You can perform a search to quickly find objects and then change their properties. You can apply different criteria that describe the object you want to search for. You can either search for the object name alone, or add additional criteria, such as the location, class, or a condition. 2. In the Search string box type product, and then click More. More options for specifying search criteria appear. 3. From the Condition list, click begins with, leave the default for the Search in box (gosales_goreatilers), and then in the Class list, click Query Item. 4. Click Search. The search is performed and a list of objects matching the search criteria was found. 5. Click the first match found in the list. The first four entries on the list are highlighted because they all point to the same item, retrieved multiple times based on the search criteria. You can now set properties for this query item using the Properties pane. Task 6. Open a project that has been modeled dimensionally and that is based on a relational data source. 1. From the File menu, click Open, and then navigate to C:\Program Files\cognos\c8\ webcontent\samples\Models\go_sales. 2. Click go_sales.cpf, and then click Open. 3. In the Project Viewer, expand Data Sources. Notice that this model references the same relational data sources that were referenced in the previous model. 4. Expand the go_sales namespace. The go_sales namespace contains multiple namespace objects.
Additional Information The Summary pane shows the statistics and tasks available for a selected object. The Statistics section shows the number of objects, by class, located in the currently selected object. The Tasks section shows actions that are applicable to the currently selected object, based on the object class.

IN TRO DUCTIO N

T O

FRA M E WO RK

M A NAG ER

5. Expand the Dimension view namespace. The Project Viewer now appears as shown below:

This namespace contains both measure dimensions, such as Inventory and Sales, and regular dimensions, such as Time and Product. This indicates that this model has been modeled dimensionally. 6. Under Dimension view, expand the Sales measure dimension. A number of sales-related measures are inside this dimension. 7. Under Dimension view, expand the Product regular dimension The Product hierarchy appears. Within this hierarchy are the levels of the Product dimension. 8. Expand the Product hierarchy. The Product levels appear.

CO G NO S

BI

M ET ADA TA

M O D EL ING

PA RT

9. Expand the Product line, Product type, and Product levels. The result appears as shown below:

The query items inside each level appear below them. These query items are added when the dimensions are created. 10. In the Project Info view, click Dimension map. The result appears as shown below:
Additional Information The Project Info view, by default is found in the middle of the user interface between the Project Viewer and the Summary panes.

We can see all of the dimensions that appear in this model. The regular dimensions are displayed with their hierarchies, while the measure dimensions are listed to the right.

3-30

2006, Cognos Incorporated Cognos Confidential. For internal use only.

This guide contains proprietary information which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language.

IN TRO DUCTIO N

T O

FRA M E WO RK

M A NAG ER

11. In the Measures list, click the Sales measure dimension. All of the levels displayed in the dimension map are highlighted. Scope relationships exist between all of these levels and the measures in the Sales dimension. 12. In the Measures list, click the Sales target measure dimension. Note that the Day level in the Time dimension is not highlighted anymore. The Sales Target measures have not been scoped down to this level. 13. Collapse the Dimension view namespace, and then expand the Database view namespace. 14. Expand the gosales namespace, and then expand the goretailers namespace. The query subjects are arranged here similarly to how they were in the gosales_goretailers project. The dimensions in the Dimension view are built as an extra layer above this layer of the model. Task 7. Open a project that has been modeled dimensionally and which is based on a star schema data source. 1. From the File menu, click Open, and then navigate to C:\Program Files\cognos\c8\webcontent\samples\ Models\go_data_warehouse. 2. Click go_data_warehouse.cpf, and then click Open. 3. In the Project Viewer, expand Data Sources. This model references a different data source that we referenced in the previous model. This model uses a data source that has been modeled as a star schema.

CO G NO S

BI

M ET ADA TA

M O D EL ING

PA RT

4. Expand the go_data_warehouse namespace, and then expand the Import view namespace. The result appears as shown below:

This data source is arranged in a star schema, with regular dimensional tables and fact tables. 5. In the Project Info view, click Diagram. 6. In the Project Viewer, right-click Import View, and then click Locate in Diagram. The Import View namespace appears in the diagram. 7. In the Project Info view, scroll down until the Fact data namespace appears. We can see that all of the dimension query subjects have relationships to query subjects in this namespace. 8. In the Project Viewer, under the go_data_warehouse namespace, expand Sales. Notice that the data items are arranged in regular and measure dimensions, as in the gosales model. Task 8. Open a project that is based on an OLAP data source. When dealing with cubes, Framework Manger is used as a publishing mechanism only. No modeling is required as it has already been done in the OLAP modeling tool which produced the cube. 1. From the file menu click Open, and then navigate to C:\Program Files\cognos\c8\webcontent\samples\Models\PowerCubes\En \great_outdoors_company. 2. Click great_outdoors_company.cpf, and then click Open.
Additional Information The Project Info view, by default is found in the middle of the user interface between the Project Viewer and the Summary panes.

IN TRO DUCTIO N

T O

FRA M E WO RK

M A NAG ER

3. In the Project Viewer, expand the Model namespace. The result appears as shown below:

We can see that there are no visible data sources. We can also see that there is only one item in the Model namespace: the great_outdoors_company cube. 4. Close Framework Manager without saving. Results: To facilitate the data modeling process in Framework Manager, we familiarized ourselves with the user interface. We opened an existing project for an operational model, examined the objects within it, examined different views of the interface, and performed a search on objects in the project. We then opened a project based on an operational data source that is modeled dimensionally, a star schema data source that is modeled dimensionally, and an OLAP data source.

CO G NO S

BI

M ET ADA TA

M O D EL ING

PA RT

Framework Manager Workflow

Data Sources

Create Project

Prepare Metadata

Model Metadata & Prepare the Business View

Create and Manage Packages

Manage Project

Publish

Set Security

Report Studio Query Studio Analysis Studio .

Content Store