Demo 1: Create a Project

Purpose:Now that we have an understanding of the Framework Manager modeling environment, we can begin developing a model that supports the business requirements of our report and ad hoc query authors. We will begin by creating a project, organizing high-level objects, and importing metadata.

Task 1. Create a project.1. Open Framework Manager.

The Welcome window of Framework Manager appears.2. Under Projects, click Create a new project, and then in the location box,

browse to C:\Edcognos\C88152\C10FM-03- Prepare_Metadata, and then in the Project name box type GO Operational.The GO Operational folder is created by default and appears by default in the Location box.

3. Click OK.The Log on page appears.

4. In the User ID box, type admin, in the Password box, type Education1!, and then click OK.The Select Languages dialog box appears. We will initially set the default and design language for this project as English.

1. Ensure that English is selected, and then click OK.The Import Metadata wizard appears. We will import metadata in a later task.

2. Click Cancel.The project opens in Framework Manager. Notice in the Project Viewer that the project appears with the name we provided and a default namespace called Model.

C O G N O S 1 0 B I – M E T A D A T A M O D E L I N G P A R T 1

Task 2. Add languages to the project.1. From the Project menu, point to Languages, and then click Define

Languages.The Define Languages dialog box appears. Notice that the project currently contains only English and it is the active language of the project.

2. In the Available Languages box, Ctrl-click English (Zimbabwe) and French, click Add , and then click OK.A warning message appears indicating that the French language will be added to every text property of every object.Adding English (Zimbabwe) is a technique we can use to preserve our original table and column names for our data source query subjects in the event that we modify them in the English and French Locales.

3. Click OK.We will now create other objects and begin to organize all objects within the model. We will rename the default namespace and create another namespace to hold our imported data source query subjects. This namespace will serve as a container for the data source view. Later in the modeling process, we will create another namespace, which will let us logically separate our model into a data source view for modelers and a business view. We will make this business view available to our report authors.

Task 3. Create and organize objects.1. Rename the Model namespace to GO Operational Model.2. Right-click the GO Operational Model namespace, point to Create, and

then click Namespace.3. Rename the new Namespace Data Source View.4. Right-click the GO Operational Model namespace, point to Create, and

then click Namespace.5. Rename the new Namespace gosales.

Creating the gosales namespace makes our data source view extensible in the event we want to import metadata from another data source. At the time of the import of the second data source, we would create another namespace to contain those data source query subjects.We will now begin the process for importing the metadata into the gosales namespace. We will start by creating a data source and testing the connection to it.

2 © 2006, Cognos IncorporatedThis guide contains proprietary information which is protected by copyright.

No part of this document may be photocopied, reproduced, or translated into another language.

I N T R O D U C T I O N T O F R A M E W O R K M A N A G E R

Task 4. Create a data source and test the connection.1. Right-click the gosales namespace, and then click Run Metadata Wizard.

The Metadata Wizard appears. From here we can select the source from which we will import the metadata. We will import data from a relational database.

2. Ensure that Data Sources is selected, and then click Next.We are now prompted to select a data source from the list of available data sources. The data source we need to access is currently not available. We must create a connection to the database from which we are importing metadata. We are connecting to the GOSALES database, which is an MSSQL Server database.

3. Click New.The Welcome page of the New Data Source Wizard appears. This is the same wizard that is used to create data sources through the Directory tool in the Cognos Connection administration interface.

4. Click Next, in the Name box, type GOSALES, and then click Next.5. In the Type list, click Microsoft SQL Server (OLE DB), leave the default

object gateway, and then click Next.6. In the Server name box, type localhost, and then in the Database name box,

type GOSALES.7. Under Signons, select the Password check box, and then in the User ID type

sa, and then in the Password and Confirm password boxes, type Education1!.

8. Click Test the connection, and then click Test.The View the results - Test the connection page appears indicating that the test succeeded.

9. Click Close, and then click Close again.10. Click Finish, and then click Close.

A new data source now appears in the list, through which we will import metadata.

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

C O G N O S 1 0 B I – M E T A D A T A M O D E L I N G P A R T 1

Task 5. Import metadata.1. Click the newly created GOSALES data source, and then click Next.2. In the list of objects, select the Tables check box, and then expand it.3. Deselect CONVERSION_RATE and EURO_CONVERSION, and then click

Next.We do not require all the metadata objects in the database; only the selected tables and the columns within them.

4. Leave the defaults for the Generate Relationship criteria, and then click Import.The import process begins, and then a message appears summarizing the count of objects that were imported.

5. Click Finish.6. In the Project Viewer pane, expand the gosales namespace.

The namespace now contains a list of query subjects, which represent each of the tables that were imported from the relational database.

7. Expand the Data Sources folder.This folder now contains the GOSALES data source, which is the data source we specified during the import. This data source is now associated with this model. We will now define a functions set for the project. It will be based on the data source from which we have imported metadata.

Task 6. Define function sets.1. From the Project menu, click Project Function List.

The Project Function List dialog box appears.2. Click Set function list based on the data source type, and then click

twice in the box under the Function set column in the GOSALES row.A list of database-specific function sets appears.

3. Click SQLServer, and then click OK.We will now create a package based on the model in its current state and publish it. We will then open Cognos Connection to view the published package, and Query Studio to view the run-time version of the model as it would appear to an ad hoc query author.

4 © 2006, Cognos IncorporatedThis guide contains proprietary information which is protected by copyright.

No part of this document may be photocopied, reproduced, or translated into another language.

I N T R O D U C T I O N T O F R A M E W O R K M A N A G E R

Task 7. Create and publish a package.1. In the Project Viewer pane, right-click Packages, point to Create, and then

click Package.The Create Package Wizard appears.

2. In the Name box, type GO Operational, and then click Next.3. Leave the default selections, and then click Finish.

A dialog box appears indicating that the package was created successfully, and prompts us to open the Publish Package wizard.

4. Click Yes.5. Ensure GO Operational is selected, and then click Next.6. If necessary, clear the Enable model versioning check box, accept the

remaining defaults, and then click Publish.A message appears within the wizard indicating that the package was successfully published.

7. Click Finish to close the wizard.A warning message is displayed in the Verify dialog indicating that the TIME_DIMENSION query subject is an "orphan." This will be fixed later in the modeling process.

8. Click Close.9. From the File menu, click Save.

Task 8. View the package in Cognos Connection and the run-time model in Query Studio.

1. Open Internet Explorer.2. In the Address box, type http:// localhost/cognos8, and then press Enter.

The Log on page appears.3. In the User ID box, type admin, in the Password box, type Education1!, and

then click OK.The Welcome page of Cognos Connection appears in the browser.

4. Open Cognos Connection, and ensure you are viewing the Public Folders tab.Notice that the GO Operational package appears as an entry within Public Folders. From the timestamp, we can see that this is the package we just published from Framework Manager.

5. Click the Query Studio link at the top right corner of the page.The Select a Package page appears, and prompts us to choose a package to use in creating the report.

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

C O G N O S 1 0 B I – M E T A D A T A M O D E L I N G P A R T 1

6. Click GO Operational.Query Studio appears in the browser. Under Menu on the left side of the page, we can see that Insert Data is selected, and that the GO Operational root namespace and the Data Source View and GOSALESaes namespaces appear. These were the objects we specified in the Publish Package wizard in Framework Manager.

7. Expand the gosales folder.The query subjects appear and are available to an ad hoc query author for creating a report.

Task 9. Create an ad hoc query.1. In the gosales folder, expand the PRODUCT_LINE query subject, and then

double-click the PRODUCT_LINE_EN query item.2. Repeat step 1 to add PRODUCT_TYPE_EN from PRODUCT_TYPE,

PRODUCT_NAME from PRODUCT_MULTILINGUAL, and QUANTITY from ORDER_DETAILS.We have successfully created an ad hoc query using the run-time model. However, notice that when we added the PRODUCT_NAME query item, we obtained a row for each language that is currently in our multilingual database. This is highly inefficient, and we will resolve this by making changes to our model so that it efficiently supports report authors who must develop reports for a multilingual audience. We will look at multilingual support in this and subsequent modules.

3. At the top of the page, click Return, click No when prompted to save the report, and then leave Cognos Connection and Framework Manager open for the workshop.

Results:We started to develop the model that will support the business requirements of our report and ad hoc query authors. We created a project, organized high-level objects, imported metadata, and examined a run-time version of the model in the reporting environment.

6 © 2006, Cognos IncorporatedThis guide contains proprietary information which is protected by copyright.

No part of this document may be photocopied, reproduced, or translated into another language.