FRAME WORK MANAGER

Introduction: Frame work manger is a metadata modeling tool for cognos server. Objects in FM: Project Model Namespace Package Dimension Query subject Query item Projects A project is a set of models, packages, and related information for maintaining and sharing model Information. A single project can span many data sources or tables.

Models
A model is the metadata layer that you import from one or more data sources. The model provides a business presentation of the metadata. A model is the set of related dimensions, query subjects, and other objects required for one or more related reporting applications.

Namespaces
A namespace uniquely identifies query items, dimensions, query subjects, and other Objects. You import different databases into separate namespaces to avoid duplicate names.

Packages
A package is a subset of the dimensions, query subjects, and other objects defined in the project. A package is what is actually published to the Cognos 8 server, and it is used to create reports and ad hoc queries.

Dimensions
A dimension is a broad grouping of descriptive data about a major aspect of a business, such as products, dates, or markets. The types of dimensions that you can work with in Framework Manager are regular dimensions and measure dimensions. In SAP BW, measure dimensions are called key figures. Each regular dimension consists of one or more hierarchies that typically contain several levels.

Query Subjects
A query subject is a set of query items that have an inherent relationship. In most cases, query subjects behave like tables. Query subjects produce the same set of rows regardless of which columns were queried. There are different types of query subjects: Data source Model Stored procedure Data source A data source query subject directly references data in a single data source. When metadata is first imported, a data source query subject is created by default for each table that you select. Default relationships between query subjects are created for you automatically. You can refine data source query subjects in various ways. Model Model query subjects can contain query items from any number of data source query subjects. Model query subjects can be enhanced by adding filters or calculations to create additional query items. You can also use query subjects from other model query subjects. Stored procedure The stored procedure query subject operates much like a data source query subject in that it Defines a set of query items that are available to the model from the underlying data source. Stored procedure query subjects cannot be enhanced by filters or calculations. Query Items A query item is the smallest piece of the model that can be placed in a report. It represents a single characteristic of something, such as the date that a product was introduced. Query items are contained in query subjects or dimensions. For example, a query subject that references an entire table contains query items that represent each column in the table. For report authors, query items are the most important objects for creating reports. The properties of query items are what report authors use to build the reports that they want.

The Project page/FM page layout: Project Viewer: Project Viewer shows the objects in a project in a hierarchical view. You can use the Project Viewer to view, modify, and create these objects: Dimensions query subjects Data sources Namespaces Parameter maps Folders Segments Links Calculations filters Packages The Explorer Tab The Explorer tab shows the contents of a project, similar to any file system. Objects can be arranged by name, class, or description. If you have a large number of objects in a project, it may be easier to locate them in the Explorer tab. You can use the Explorer tab to view, create, and modify objects and relationships. You can also create folders and namespaces to group objects. The Diagram Tab The Diagram tab uses a diagram to show the relationships between objects in a project. Relationships between objects are shown as lines with cardinality notation. You can expand objects and namespaces to show the object hierarchy and the relationships between objects. The Dimension Map Tab You can use the Dimension Map tab to view, create, and modify hierarchies and levels for the dimension you selected in the Project Viewer. You can also view and modify scope relationships. The Use Use You Measures and Attributes tabs appear after you click the Dimension Map tab. the Measures tab to view all the measures that are available in the model. the Attributes tab to view or modify the role of the select query item. can also embed calculations in the query item.

The Properties Pane The Properties pane shows the properties of the objects that you last selected in the Project Viewer, Explorer tab, Diagram tab, Dimension Map tab, Search pane, or Summary pane. Object properties are set during import, and some property values can be modified during modeling. You can use the Properties pane to add, modify, or delete the properties of objects. You can modify the properties for multiple objects at one time. If you select more than one object,

The Summary Pane The Summary pane shows the language, statistics, and tasks available for an object that you selected in the Project Viewer. The Project section shows the design language and the active language. You can change the active language. The Statistics section shows the number of objects, by class, located in the currently selected object. If the selected object contains a folder, the contents of the folder are included in the number count. Selected objects include projects, namespaces, and folders. The default selected object is the project. The Search Pane When you are working with a large project, it can be difficult to locate the objects that you need to complete a task. Use the Search pane to quickly find objects by applying different search criteria, such as the location, class, a condition, or a property. If you need more room, you can resize the Search pane or move it so that it floats in the window.

Project Files:
<project name>.cpf Model.xml Preferences.xml Customdata.xml repository.xml The Framework Manager project file, which references the .xsd And .xml files used to define a project The actual model data created by Framework Manager users The preferences for Framework Manager projects The stored diagram information, such as the diagram layout, Notation, font, and color The logged version history for each project or segment that was Added to a repository. This file exists only if you added projects To a repository.

Importing meta data from different sources:

Relational databases, such as Oracle, DB2, and Microsoft SQL Server SAP BW data sources Existing Cognos 8 models Architect models and Impromptu catalogs Decision Stream or Cognos 8 Data Manager models Third-party metadata sources XML as a data source

Segment A segment is a project within a root project. A segment is owned by its root project and is not shared by other projects. You can create a segment so that you can organize a project according to business rules and organizational requirements share and reuse project information

Linking A link is a shortcut to an existing project. The project that is linked may be shared by Multiple projects. Repository Control Use repository control to help manage your projects in Framework Manager. You control versions of a project to ensure that each version of a file is recoverable. Repository control also ensures that users in a large organization have access to the most recent changes or versions of a project or segment. You can use Framework Manager to create a connection to a Visual SourceSafe (VSS) or Concurrent Versions System (CVS) repository add a new project to a repository add an existing project to a repository create a local project from a repository After your repository has been set up and projects have been added, you can use Framework Manager to check in and check out a project get the latest version of a project view project history We do not recommend synchronizing projects that are connected to repositories. For more information, see "Synchronize Projects" Note: The limitations set by the third-party repositories are incorporated into Framework Manager. For more information, see the vendor documentation for the third-party data source. Synchronize Projects You can use Framework Manager log files to synchronize your project. You may choose to synchronize your project if you updated metadata in a third-party modeling tool made changes to metadata using a multidimensional modeling tool When you synchronize your project, you create a new project by replaying from the log files, all the actions you made in the original project. Special considerations should be taken before synchronizing projects that contain Segmented models linked models Repository connections

Improve Performance by Setting Query Processing Type The query processing property for data sources determines whether SQL processing is performed by the database server or if it is processed locally. For relational metadata, you can improve performance by selecting the right type of query processing.

There are two types of query processing: Limited local The database server does as much of the SQL processing and execution as possible. However, some reports or report sections use local SQL processing. Database only The database server does all the SQL processing and execution. An error appears if any reports or report sections require local SQL processing. Detecting Cardinality from the Data Source When importing from a relational data source, cardinality is detected based on a set of rules that you specify. The available options are use primary and foreign keys use matching query item names that represent uniquely indexed columns use matching query item names 0: 1 - 0 is the minimum cardinality, 1 is the maximum cardinality 1: n - 1 is the minimum cardinality, n is the maximum cardinality Regular Dimension A regular dimension contains descriptive and business key information and organizes the information in a hierarchy, from the highest level of granularity to the lowest. It usually has multiple levels and may have multiple key segments to define a level. It may also have multiple hierarchies. Balanced hierarchy: Each path in a balanced hierarchy descends to the same depth. UN balanced hierarchy: The branches in an unbalanced hierarchy descend to different levels Measure Dimension A measure dimension is a collection of facts such as Quantity Sold or Price. You can create a measure dimension from one or more query subjects that have a valid relationship between them. When used in a report or analysis, the measure dimension shows the value of the query item such as a name or number, or shows null, zero, or invalid.

Scope Relationships A scope relationship defines that measure dimensions and regular dimensions can be related for reporting purposes. If you set the scope relationship for the measure dimension, the same settings apply to all measures in the measure dimension. If data is reported at a different level for the measures in the measure dimension, you can also define a scope relationship for each measure. You can specify the lowest level that the data can be reported on. The purpose of scope relationships is to govern inclusion and exclusion of a dimension and certain levels in the hierarchy of that dimension for a particular fact. Scope relationships should always be set at the level of the underlying relational join or higher. If you set the scope of a dimension at a level below the level of the join to the relevant fact, the lowest level values in the fact are repeated for the levels of the dimension below the join level. Specify a Determinant A determinant is the set of query items that can be used to uniquely identify a set of data. Determinants are imported based on key and index information in the data source. We recommend that you always review the determinants that are imported and keep only the ones needed to control granularity. Determinants are used only with query subjects. Use a determinant when you want to do any of the following: Add information about functional dependencies between columns to avoid doublecounting. Specify the granularity of a demoralized query subject to control grouping and Double-counting when using model dimensions. For example, some facts join to time on month and some facts join to time on day. Specify Determinants for time to clearly capture the functional dependency between month and day to Prevent double-counting for those facts that join at the month key. Uniquely identify the row of data when retrieving text blob data from the data source. Override the determinants imported from the data source that conflict with relationships Created for reporting. For example, there are determinants on two query subjects for multiple columns but the Relationship between the query subjects uses only a subset of these columns. Modify the Determinant information of the query subject if it is not appropriate to use the additional Columns in the relationship.

Types of SQL:

Properties of Query Items:

Usage Property

Calculation Use a stand-alone calculation when you want to reuse the expression. You can apply a stand-alone calculation to one or more dimensions or query subjects to provide calculated data to a report, or include it in a package to make it available to your users. By moving a stand-alone calculation or a shortcut to it into a folder, you can better organize the model objects. Use an embedded calculation when you want to use a calculation with only one dimension or query subject. You can create an embedded calculation when modifying a relational data source query subject, model query subject, or dimension. If you start with an embedded calculation, you can later convert it into a stand-alone Expression that you can apply to other dimensions or query subjects. Prompts

Shortcuts

A shortcut is a reference to an object, such as a relationship, a dimension, a query subject, or a folder. We recommend that you use shortcuts in the business view when there is an overlap between user groups and you want to include the metadata in more than one folder. With shortcuts, you can have multiple references to an object. Star Schema Group Star schema groups can make the model more intuitive for end users by indicating which regular dimensions and measure dimensions are related. Star schema groups can also facilitate multiple-fact reporting by indicating how to use regular dimensions that are common to many measure dimensions. Multiple-fact reporting is also known as cross-functional reporting. Star schema groups also provide context for queries with ambiguous joins. By creating star schema groups in the business view of the model, you can clarify which join path to select when multiple join paths are available. This is particularly useful for fact-less queries. In a star schema design, numeric, transactional data is contained in a central fact table with related dimension tables radiating out from the fact table. Star schema groups can contain the selected dimensions, query subjects, or shortcuts. The objects in a star schema group cannot reference, or be referenced by, any object outside the group. Therefore, Framework Manager automatically creates a shortcut for any object that is referenced by an object outside the group. Set Governors Use governors to reduce system resource requirements and improve performance. You set governors before you create packages to ensure the metadata in the package contains the specified limits. All packages that are subsequently published will use the new settings. There are a number of governors that you can set. Governor settings in the model can be overridden by governor settings in Report Studio. Report Table Limits You can control the number of tables that a user can retrieve in a query or report. When a table is retrieved, it is counted each time it appears in the query or report. The limit is not the number of unique tables. If the query or report exceeds the limit set for the number of tables, an error message appears and the query or report is shown with no data. A setting of zero (0) means no limit is set. Data Retrieval Limits You can control the number of rows that are returned in a query or report. Rows are counted as they are retrieved. When you run a report and the data retrieval limit is exceeded, an error message appears and the query or report is shown with no data. You can also use this governor to set limits to the data retrieved in a query subject test or the report design mode. A setting of zero (0) means no limit is set.

If you externalize a query subject (p. 218), this setting is ignored when you publish the model. Query Execution Time Limits You can limit the time that a query can take. An error message appears when the preset number of seconds is reached. A setting of zero (0) means no limit is set. Large Text Items Limit You can control the character length of BLOBS (binary large objects) that a user can retrieve in a query or report. When the character length of the BLOB exceeds the set limit, an error message appears and the query or report is shown with no data. Allow Enhanced Model Portability at Run Time You can use a separate but structurally similar data source at run time. The database schema must be the same between the two data sources. This governor is selected upon initial upgrade. It prevents rigid enforcement of data types so that a Cognos 8 model can function as a Report Net 1.x model until you update the data types in the metadata. It ensures consistent behavior with Report Net 1.x by deriving a form of dimensional information from the relationships, key and index information in the data source. By default, the model is not portable at run time. If you select this governor, Cognos 8 retrieves metadata from the data source and caches it instead of using the metadata already cached in the model. If you do not use this governor, you must ensure that the following metadata are the same in the original and new data sources: Collation sequence name Collation level Character set Null ability Precision Scale Column length Data type Allow Dynamic Generation of Dimension Information Select this governor upon initial upgrade of a Report Net 1.x model. This governor allows Consistent behavior with Report Net 1.x by deriving a form of dimension information from the Relationships, key information, and index information in the data source. Allow Usage of Local Cache Select this governor to specify that all reports based on this model should use cached data. By default, this governor is disabled. After the governor is turned on, the model must be republished for the changes to take affect. This setting affects all reports that use this model. If you want a report to use a different setting than the model, you can do this in Report Studio. For more information, see "Improving Performance by Reusing Cached Data When Running a Report.

Outer Joins You can control whether outer joins can be used in your query or report. Cross-Product Joins You can control whether cross-product joins can be used in your query or report. A cross-product join retrieves data from tables without joins. This type of join can take a long time to retrieve data. By default, this governor is set to deny. If you want to allow cross-product joins, click the check box. Use with Clause When Generating SQL You can choose to use the with clause with Cognos SQL if your data source supports the with clause. The With clause will be turned on for models created in Cognos 8. For upgraded models, it is turned off unless it was explicitly turned on in the Report Net model prior to upgrading. Security in Framework Manager: Data security You create a security filter and apply it to a specific query subject. The filter controls the data That is shown to report authors when they set up their reports. Object security You secure an object directly by allowing users access to the object, denying users access to the object, or keeping it hidden for all users. Package security You apply security to a package and identify who has access to that package.

Fact less Fact table: Fact less fact table is nothing but a fact table which doesnt have any measures These are two types Coverage: it is use full for when pk fact table is sparse. Event track: the meaning of this is tracking the event.