Tuesday 29 October 2019

Content Store Tables

Here are some information on the content store tables with a couple of edits. The sources are found in the links below. Credit (or blame :)) goes to them.

CMOBJECTS - content store objects (as of v11)
CMCLASSES - object type (report view = 19, etc)
CMREFNOORD1 - reference table. Here the report source of a view can be obtained.


https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014692216


http://it.toolbox.com/wiki/index.php/Cognos_Content_Store

Cognos Content Store Database Tables Table name Description
CMSYSPROPS This table has the Content Store Version.
CMOBJNAMES This table has the names of all the objects in the content store.
CMOBJPROPS1 Users, Roles \ Group Distribution list and contact information such as Email, phone number, Fax Given name etc are stored in this table
CMOBJPROPS2 Report scheduling information is stored. This table has fields like hour, day week etc
CMOBJPROPS3 Stores Screen Tip and Object description provided while creating the objects are stored here
CMOBJPROPS4 Stores the printer paper setting details like height and width of A3 , A4 , letter and 11X17 paper orientations
CMOBJPROPS6 Has the details of the all packages which were published using the FM.
CMOBJPROPS7 This table stores the XML of all reports and models. This is basically to maintain the metadata about the structure of the reports and models.
CMOBJPROPS10 Contact information is stored in this table. This table has columns like Contact Email and Contact.
CMOBJPROPS11 This table stores the data sources configuration details like connect string, the cube location etc.
CMOBJPROPS13 It stores the names of parameter passed to the range prompts.
The binary value in CPARMVALUE is XML compressed with gzip.
CMOBJPROPS14 Has details regarding the versions, creation time etc of the objects in the content store.
CMOBJPROPS16 This table provides the status of the multiple services of Cognos like LogService, MonitorService, ReportService, SystemService, JobService
CMOBJPROPS17 Stores performance details of each component like “query Studio, Analysis Studio, Event Studio” etc
CMOBJPROPS18 This table stores the drill path from the source to the final target report.
CMOBJPROPS20 Stores details regarding which are all the reports for which prompting has been enabled. And also has the details of which are the reports which has the default report options overridden.
CMOBJPROPS24 Stores the printer configuration details
CMOBJPROPS25 Stores the data regarding the objects deployed, like the deployed folder, the reports, the number of folders present in the deployment archive, etc
CMOBJPROPS26 This table stores the data about all the packages imported / exported in C8, with the properties selected during the process.
CMOBJPROPS27 Has the details regarding the data source created in the content store using Cubes.
CMOBJPROPS30 Stores the registration , service description etc details about portlets in this table
CMOBJPROPS31 Has the custom logging level for each of the Cognos services, CMID can be be linked to CMOBJNAMES for the names of each of the services
CMOBJPROPS32 Has the details of the stored procedures used as the query items in the FM model.
CMOBJPROPS33 Detail related to users, user groups user roles.
CMOBJPROPS34 Has the details regarding the drill through parameters of the drill through reports. The parameter assign values are present in coded format
CMOBJPROPS36 Has the list of all the Models published using framework manager
CMOBJPROPS37 This table has the details of the routing sets configured for server / load balancing for each package published in the content store
CMOBJPROPS38 Configuration details about number of items to retrieve in studios, for a package are saved under this table.
CMOBJPROPS39 Has values for properties of reports and views. PROPID can be linked to CMPROPERTIES for property names
CMOBJPROPS52 Contains the properties for the connections
CMOBJPROPS55 Has the URI for icons for each entry in Cognos Connection
CMLOCALES Has the locale ids associated with each language supported by Cognos 8

Friday 12 April 2019

Define Data Server Connection in Cognos v11

for Microsoft SQL Server:

JDBC URL is:
jdbc:server://<server name>\<instance>:<port number>;DATABASE=<database name>

This is the format I was able to make it test successfully. Make sure your port number is correct. To find out SQL server port, please see previous post.

This also worked:
jdbc:server//<server name>:<port number>;DATABASE=<database name>;INSTANCENAME=<instance name>

You can also use a datasource connection already defined in Cognos Administration provided the JDBC connection for that datasource is enabled and configured (DQM enabled). You just have to check the Allow web-based modeling checkbox. You can find this checkbox in Connection tab of Properties for the datasource.

Friday 22 March 2019

Avoid Detail Filter in Page Set

Here is a cool puzzle posted by CommandoCognoise and fully solved by CognosPaul in cognoise.com

The simple report displays a crosstab with two sets of rows, [Product] and [Sales Employee]. Columns consist of [Year] and measure is the [Sales].

However there is a requirement to display the crosstab across multiple pages per employee. Thus page 1 will look like:


and page 2 will look like:

At first glance, the requirement could easily be accomplished using page sets grouped by [Sales Employee] and creating a master-detail relationship on that column. However this will result to the [Product] getting filtered by the specific employee.

To get around this, I nested the [Product] row with the root member of [Employee] dimension.

Nesting the columns with the [Employee] root member will also work.

But there is another solution which will not require nesting the rows or column. This is particularly useful if the format is required as the report is getting exported to excel to be processed further.

First step is to create another query with an [Employee] data item. This will be used for the page set.

The second query is the one which contains the items to be used in the crosstab. Add a data item calculation which looks like:

#prompt('emp','mun','[MUN OF ROOT MEMBER OF EMPLOYEE]')#

Replace the [Employee] row with this data item. The last step is to replace the master-detail relationship linking the [Employee] data item from the first query used in the page set with the 'emp' parameter.

One coolest solution!

Wednesday 13 March 2019

DQM in Cognos Analytics

MS SQL Database

As of Cognos 11 sqljdbc4.jar is only needed in <install folder>\drivers

Do not put in <install folder>\v5dataserver\lib nor in <install folder>\webapps\p2pd\WEB-INF\lib
Doing so will generate a BMT-IMP-0002 CAF-WRN-2082 error when adding a Query Item in Framework Manager.




Defining both instance name and port is ok. Make sure you know the port number. If not, use this query to find out the port number:

select distinct local_net_address, local_tcp_port
from sys.dm_exec_connections
where local_net_address is not null

If the user credentials is not authorized to run that query, then for now you are out of luck.

Datasources with jdbc connector can also be used as data servers by checking the "Allow web-based modeling" box on Connection tab in datasource properties section.

In your Framework Manager model, you can set the query mode property to DQM or Compatible mode by selecting the Project and changing the query mode property.



Thursday 7 March 2019

Cognos Analytics Prevent View Link Breaks

I'll edit later. For now I need to save this link

https://www.ibm.com/communities/analytics/cognos-analytics-blog/administration-changing-the-behaviour-of-object-copying-in-cognos-analytics-11-0-7-release-7/

Tuesday 5 March 2019

Install Cognos v11 with Single Sign On

In this post, I will put in detail the steps how to install Cognos v11 with single sign on (SSO) capability. I will also write down the issues I encountered as well as the solutions to the said issues. Note that I was installing Cognos Analytics for Windows 64bit version 11.0.13. I'll add another note as well that we do not require dynamic query mode (DQM) so I don't know if there are additional files needed for DQM.

Since we were using Microsoft SQL Server for our backend as well as our content store database, the first thing to do is:


  • Download the SQL Server driver. The file you required is sqljdbc4.jar. 


After several attempts to install trying out different options, the only way I was able to make SSO work smoothly is to


  • Install using custom installation and select all components. Particularly include optional gateway.
Before running Cognos Configuration,

  • Copy the sqljdbc4.jar in <install folder>\webapps\p2pd\WEB-INF\lib
or any folder which is included in the java path like <install folder>\drivers. The first folder I mentioned has .jar files in it so the sqljdbc4.jar seems to be at home in that folder. Again, do this only if you will use MS SQL Server database.

** this cause BMT-IMP-0002 CAF-WRN-2082 error when importing tables in Framework Manager. Try to copy sqljdbc4.jar in <install folder>\drivers instead.
  • Run Cognos Configuration.
You only need to configure your content store and authentication (we use LDAP). And while you are in authentication, might as well disable anonymous login. Start your Cognos services and test by logging in to:

http://<servername>:9300/bi/v1/disp

If you can open this page successfully and login, you are half way through.

  • Download the IIS automated script here:
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.inst_cr_winux.doc/t_gateway_iis.html

You can initially follow the instructions manually. You will appreciate the script a lot more if you do. And it is a great learning experience.

appcmd list app
appcmd delete app