Cognos 8.

4 framework Manager
1. Datasource Creation Step 1: Cognos Administration portal. Launch --> cognos administration --> Configuration tab --> Data source connection --> odbc --> Dsn name (which we created in control panel--> odbc --> system dsn). Step 2: Test the Connection. Note: we can create a datasource in another way in framework manager itself.In the metadata wizard data source, you can create a new datasource. 2. Framework Manager Application Creation Step 1: File --> New.(give new framework manager project name). Note:1 List of recently used four projects will be displayed in FM after clicking the framework manager module in start--> IBM cognos ---> framework manager. Note:2 we can remove list of recently used projects by <installationlocation>\c8\configuration\bmt.ini and make sure your editor is set to save the file with UTF-8 encoding. Step 2: Choose English Language. Step 3: In Metadata Wizard, Select metadata source --> Data sources --> Select datasource which you created. Step 4: Choose the database and select tables which you want to use in your application. Note: Default Namespace will be created based on your database's datasource name. namespace is a container which holds query subjects. Step 5: After getting the tables in your design, click the diagram on the right side and click the relationship button on extreme right. put the cardinality. cardinality must

then only you can get correct value.this step we can establish a join between the tables. Step 6: for formatting the column, select the column on the query subject and click the formatting on properties windows of second bottom. Step 7: All Query Subjects has got data items. some data items has "L" symbol which means measures. we can assign data item as measure,identifier(relationship columns or numeric column),Attributes means data item which has strings like names,dates. Step 7: create a package for creating reports. while creating package, we need to select only our tables database function list in function lists dialog box. Step 8: choose the location where you can store the package. whether you want to save the package in public folder or my folder. Step 9: Save the Framework Manager Project file. Note: framework manager project file is composed of .cpf and some xml files. 3.Testing Framework Manager Models First Method: Right click the tables and select test for testing the table. Second Method: Select different data items from different query subjects using ctrl and select the data items and right click test. You can verify results and we can make sure proper relationship established or not. 4.Adding New columns in the existing Query Subjects
----------------------------------------------------1.Select the query subject. 2.Goto Tools Menu --> Update Object.

5.Framework Manager Suggested Model Techniques

-------------------------------------------------

Database Layer - database tables. Business Layer - database tables+query subjects. Presentation Layer - Query Subjects Short cuts.publish this package as a main package for reporting.

6.Difference Between Folder and Namespace.

---------------------------------------------Folder can not have same name of query subjects. Namespace can have same name of query subjects. 7.Three Types of Query Subjects in the model ------------------------------------------------1. Data source.(importing from tables) 2. Model.(importing from existing query subject's dataitem) 3. Stored Procedure.(importing from oracle/sql server's stored procedure). 8.Parameter Map - to implement row level security and dynamic database selection. 9.Framework Manager filter types - Embedded Filter & Standalone filter. 10.we should not change the namespace name.if you must change a namespace name,you should analyze the impact of publishing your package with the changes by right clicking the package and choose analyze publish Impact. 11.Adding datasource using metadata wizard will add more than one query subjects but using datasource query subject wizard will add only one query at a time. 12.we can create query subjects in two ways. 1.Right click the namespace and select query subject.(we can not update newly added column from the table,for this, we can modify the query definition. first we need to delete all the columns in select statement and add only select * like this). 2.In metadata wizard is another way of creating query subjects, we can update the newly added column in query subject using tools --> update object. 13.We can filter the query subject,for this, double click the query subject and select the filter tab and add the filter. we can add mulitiple filter in a single query subject using "AND" Statement.

14. Determinants in Framework Manager --------------------------------------Granularity is a simple concept describing the level data relates to. Level1: Country Level2: Sales Area Level3: State Level4: City Level5: Store Level6: Department Level7: Employee We can summarise sales volume (quantity) at each of the levels above. The level at which we report is the grain (or granularity) of the table. Tables or query subjects in Framework Manager often have multiple levels (grains) which you may have to join to another table with a different level grain. An example of this is budgets. Using our example above, we want to join our sales area table to our budgets table. Unfortunately the grain of the sales area table is employee but the budgets have been completed at Store level.

In Framework Manager, if we join directly from store in sales areas to store in the budget data the budget data value will be repeated for how many employees are part of that store. New Query Subject (join on Store with no determinants set): Sales Area.City Sales Area.Store

Budget.Month Budget.Sales_Target

As there are four employees at the Bayside store this forces the model query subject to return four rows repeating the sales budget. To correct this Framework Manager has to be instructed what level of granularity the budget applies to. This is done using determinants. In our example we need to set the determinants on the Sales Area query subject. Right click the query subject and select the determinants tab. One determinant should be created for each level of granularity as shown below. Create the determinant by clicking Add. Rename the determinant and then drag the identifying column (Key) into the key window (bottom left). If the level has any attributes that exist at the same level of granularity these should be added to the Attribute window. If the new determinant you have created is the lowest level grain (Employee in this case) the Uniquely Identified check box should be ticked. The Group By tickbox should be ticked if the level is ever to be used for aggregating values. Ensure that once you have created all of your determinants for the query subject that they are in the correct order (use the up and down buttons to sort them correctly).

After setting the determinants click OK to save the changes. When the model query subject is now run, only one row of data is returned:

15.