C8 and C7 comparison

C8 and 7 comparison

I am just curious how the XML tag organization was different between the cognos 7 and cognos 8 version. Since my client is in the verge of migrating to Cognos 8 environment. I was just comparing both the XML tags for a simple report. For comparison to be simple, i created a simple list report with 4 to 5 columns both in cognos 7 and 8. First i took the Query section alone, which usually will come before the report layout.

1) Since tabular model concept was not there in Cognos 8 there is no tag named in cognos 8.
2) Cognos 8 report will directly access the data item from query, so Cube, dimension and factlist tags are not present in C8.
3) The hierarchy of Query in C8 is
Queries > Query > Selection > Data Item.

Whereas in Cognos 7
QuerySet > BIQuery > Cube > Factlist and Dimension
> Tabular model > data item
4) There is one tag called Source in the query, i need to explore this. Will do in upcoming blogs if i come to know any.

Thanks and Regards,
Soma

Cognos Java Script Learning I

I am now expanding my knowledge on using Java Script in the Cognos ReportNet. I have gone through the following Cognos help link which describes the code to clear the selections from multiple multi-select boxes with a single click.

We have to use the following Javascript in the HTML Item to deselect the selections of a List Box.

listBox_..._deSelectAll() for all the list boxes.

I am writing a custom function in Java Script called ClearAll() which will clear the all the list boxes referring inside the function.

function clearAll()
{
listBox_Parm_Region.deSelectAll()

listBox_Parm_Product.deSelectAll()

}

In the above function Parm_Region and Parm_Product are the list box name in the Prompt page.

I am calling that function on the click of one button. The following code is used to add a button in the prompt page. When clicking that button, function ClearAll will be executed.

" <button style="" class="clsPromptButton" onmouseover="this.className = 'clsPromptButtonOver'" onmouseout="this.className = 'clsPromptButton'"

onClick="clearAll();">Deselect All "

http://support.cognos.com/knowledgebase/googlesearch?load_kb_document=1&dr=kb1&uniqueid=134543

I didn't triy the above code. I just skimmed and i understand the functionality. I have to try the above code soon.

Creating IQDs through FM

I was just skimming through the questions of Cognos community in Orkut.
I saw a thread where the user asks whether we can create IQD using Framework manager?

Please find below for my response. Yes we can create IQDs from Framework manager.

In the business layer make sure you have included all the columns from different tables to the query subject.Click on the properties of the Query subject in Business layer. You will find a property called Externalize Method: Change it from default to IQD.While publishing the package, the publish package wizard there is a place where you have the local/physical file path where you need your IQDs to be created.

Thanks and Regards,
Soma

Calculated Data Item in Cognos ReportNet

Today i have a requirement in my project. I need to generate a sales report for products which includes grouping at all levels of the product hierarchy. I need have a group footer which will show the corresponding measures summary for the particular level of grouping. As for as the numerical fields from the database are concerned i know the ReportNet column will calculate the sum at the corresponding levels if we give aggregation 'TOTAL' at Cube(Query) Level. I need to calculate the percentage based on 2 columns from Database. There is no problem in the detailed rows as for as the calculation is concerned. but when it comes to show the percentage at the sub group summary. I am not aware of using the aggregation = 'CALCULATED' property at Cube (Query) level. So for i am using the work around, I will calculate the totals for each sub group level in a data item and use it in another data item to calculate the percentage at the corresponding levels. This will definitely affect the performance of the report since the number of Data items and Calculations are more in this kind of approach.

So if we give Aggrgation proprty of a Data Item both at TMOD and Query level, we can use the particular calculations even in the Sub grouping level summaries.

Your feedbacks and Comments are welcome as it will provide a way to improve. May be my insight says my english is not much good. I am working on that, Please excuse.

Master Detail Relationship in Report - Check the Filter condition of the Master query before including the detail query

For last couple of days i am working on the Master Detail Report. I heard Master Detail Reports involve outer joins in the Report which will affect the performance drastically. We have explained this scenario to our customers. We cant achieve the requirement of Customer without the Master Detail Query. Customer has accepted for this, since they compromised on the Prompts they are going to select are few. I have added a in the report. I tried to include a parameterized detail query, It shows a error when i am selecting the parameters for detail query since the filter condition for Master query is not valid. Later i modified the Master Query filter, then i am able to include the detail queries. Now only i know that the parameter filters of Master Query is validated before ReportNet it let us to include the detail query.

Cognos ReportNet Architecture

Cognos ReportNet

Cognos ReportNet uses Platform Independednt technologies such as
1) XML -Extensible markup Language
2) SOAP - Simple Object Access Protocol
3) WSDL - Web Services Definition Language

ReportNet Architecture:
We have 3 layers in the Cognos ReportNet: Web Server, Application Layer and Data Layer

User Interfaces:
Following are the interfaces through which we can access Cognos ReportNet.
* Cognos Connection
* Report Studio
* Query Studio
* Framework Manager

In the above four except Framework Manager (FM) all are web based whereas FM is windows based.

Cognos Connection:
1) Public Folders:
2) My Folders:
3) Directory:
4) Capabilities:
5) Schedule Management:
6) Server Administration:
7) Deployment:

Cognos Application Firewall and ReportNet Gateway - Tier 1 Web Server layer

Cognos Application Firewall:Cognos Firewall in addtion to the organization Firewall provides high levl secutiry to ReportNet on top of ReportNet Gateway.

ReportNet Gateways:
Following are some of the gateways supported by Cognos ReportNet - CGI, ISAPI, APACHE_MOD and SERVELET.

* CGI Gateway: It is the default gateway supported by all webservers. It delivers slow performance.
* ISAPI: It is used for Microsoft IIS -faster with MS IIS.
* APACHE_MOD: With Apache Web Servers
* Servelet: To use this gateway, Your web servers should support this.

When a ReportNet gateway receives a request, it encrypts passwords to ensure security; extracts information needed to submit the request to a ReportNet server; attaches environment variables.

Tier II - Applications - ReportNet Server
Runs the Reports and Queries forwarded by ReportNet Gateway.
Renders the Cognos Connection Interface.
Content Manager - which manages ReportNet Information.
Dispatcher - operates services and route requests.

Content Manager:
1) It stores all ReportNet information in Relational Database (Content Store).
2) We can install Content Manager any number of times for a ReportNet Installation, But only one is active at any time.
3) Following are the information stored by Content Manager:
Reports - Report Specs, Properties, Security Settings and outputs.
Packages - Metadata, Reports and Folders
Server Configuration - Directory information, Cognos Namespace, Information about contact, Distribution Lists, Data Sources and Printers.
Personal User Information - It consists of My Folders and My Pages.
4) It contains names, descriptions and tool tips in different languages to support Multilingual Capabilities.
5) It also Performs Content Store Management Functions such as Export and Import.

Content Access Manager: Primary Security component of ReportNet.
#) It Provides ReportNet with a consistent set of Security Capabilities and APIs - Including authentication, authorization and encryption.
#) Some security capabilities, such as user authentication, are external to ReportNet but are exposed to ReportNet by Access Manager.
#) Other capabilities, such as authorization, are internal to ReportNet, and are implemented by Access Manager.
#) For many security-related functions, Cognos Access Manager requires certificates and interacts with a Certificate Authority.
Dispatcher:
1) Starts all ReportNet Services configured in the computer, routes the requests, distributes configuration changes.
2) It is a Multi Thread application, which uses one or more thread per request. 3)
3) When a dispatcher starts, it registers itself with the content manager.
4) The Services managed by dispatcher includes the following:
Presentation Service, Batch Report and Report Services. Job and Schedule Monitoring Service and Log Service.
Presentation Service - Used in cognos Connection and Query Studio.
* Accepts the User imformation
* Stores and Retrieves information in content Manager.
* Creates Cognos Connection page in Report Viewer

Batch and Report Services - Used to run reports and retrieve Metadata from Content Manager.
It also includes many components like Metadata Service, Query Engine and PDF engine.

Job and Scheduling Service - It manages the scheduled jobs and reports, which are run y Batch service. It also send e-mail.

Log Service - manages all logs generated by the dispatcher and other services.

TIER III- DATA CONTENT STORE
The ReportNet data tier contains the content store which may be anyone of the RDBMS.

It is used by content manager to store the information that are visible and mabager through cognos Connection. Information stored in the Content Store may include - Packages, Folders, Reports, Saved outputs, Directories, Server Coonfigurations and ReportNet Deployment.
Content Manager user JDBC API to access the content store. ReportNet comes with respective JDBC drivers specific to different Databses available in the market.

Cognos does not publish the content store schema. It periodically updates the schema isolating the changes from the user through stable user interfaces and API.

Much of the information in Content Store, Such as Report Results and XML report specs are stored as Binary Large Object Fields (BLOB). All the report outputs in different formats are compresses and stored in content store. Content Manager uncompresses when it is sending to User.