Category Archives: Cognos

Basics of Cognos Part 1


In this post we will learn to create some basic reports in Cognos 10.2. Since this is very first post on Analyticsquare for Cognos category. Before start let’s have a look on few concepts of Cognos.

  • Cognos Connection: IBM® Cognos® Connection is the portal to IBM Cognos software. IBM Cognos Connection provides a single access point to all corporate data available in IBM Cognos software. You can use IBM Cognos Connection to work with entries such as reports, analyses, queries, agents, metrics, and packages. You can use IBM Cognos Connection to create shortcuts, URLs, and pages, and to organize entries. You can personalize IBM Cognos Connection for your own use. You can use IBM Cognos Connection to create and run reports and cubes and distribute reports. You can also use it to create and run agents and schedule entries.

Cognos Connection Framework Manager: IBM® Cognos® Framework Manager is a metadata modeling tool that drives query generation for IBM Cognos software. A model is a collection of metadata that includes physical information and business information for one or more data sources. IBM Cognos software enables performance management on normalized and de-normalized relational data sources and a variety of OLAP data sources. When you add security and multilingual capabilities, one model can serve the reporting, ad hoc querying, and analysis needs of many groups of users around the globe.
Framework_Manager Up to this point we have a basic idea about Cognos connection and Frame work manager. Before creating a report we should know about Packages in Cognos reporting.

“Metadata is published for use by reporting tools as a package, providing a single, integrated business view of any number of heterogeneous data sources.”

At our first step of Cognos report let’s create a Package.

Step 1.  Open Frame work Manager you will see the above screen. Click on Create a New Project which will open one dialog box, set the location where you want to save this project and click OK button SaveProject






Step 2. The next dialog box will ask you the language (I am choosing English).













Step 3. The next dialog box will open to choose Meta Data Source for your Project, I am choosing Data Sources for this and click next.














Step 4. In this step we will either choose a previously created Data Source or create a new one. In our case we will create a new data source. This will again open a Wizard, click on Next. The next screen for given the name of Data source. I have assigned SQLServerDS name to it and click on Next button and choose Microsoft SQL Server (OLE DB) as Type and click on Next. SelectDataSource





















Step 5
. Fill the details of Server and Database name as per below screen. At the bottom of this screen you test this connection. And click on Finish button. Now you are ready with your newly created data source. Select this data source and click on next.


Step 6. Now this window will lets you the freedom to select the database objects. Select the objects whichever you want to import in this data project and click on Next.














Step 7. At this step we can define the relationship among the objects. Framework Manager can create relationships between objects in the model based on the primary and foreign keys in the data source. You can create or remove relationships in the model so that the model better represents the logical structure of your business.

After you import metadata, verify that the relationships you require exist in the project and that the cardinality is set correctly. The data source may have been designed without using referential integrity. Often, many primary and unique key constraints are not specified. Without these constraints, Framework Manager cannot generate the necessary relationships between fact tables and dimension tables.

Framework Manager stores relationships in the nearest common parent of the objects that participate in the relationship. The parent can be either a folder or a namespace. If you move one of the participating objects outside the common parent, the relationship moves to the next namespace that is common to both ends of the relationship. If you move a relationship to a different folder or namespace, the participating objects also move to the same folder or namespace.

Click on Import and finish. Relationship













Step 8. Using above screen is to check the all imported objects and create new package. When you expand SQLServerDS you will see all the imported objects and expansion of data sources will give you list of all created data sources.

Step 9. Now in this step we will create a new package. For this just do right click on Packages and click on create package this will show the below dialogue box give the name of your package and click on Next.














Step 10.  The next screen will give you the freedom to choose objects used in this Package and when you click next you can select all available functions. Now click on finish. When you click on finish a new dialogues box will open which will ask you to publish your package click on Yes.


Package3 Package4





























Step 11. When you click on Yes then below screen will open which will give you freedom to choose the destination folder where to deploy this package. When you will set all these options click on next.













Step 12. When you click on Next on above screen it will ask you to set user access who can access the package. When you will set this click on next and then finish.

Now you can see this package on frame work manager as well as on Cognos connection.


Cognos Connection_Last