Blog

What's happening? What's new? What can I do? Find answers to these questions in the blog.

Archive Results

Blog

New Base Samples for IBM #Cognos Analytics 11.0.11

There are two types of samples that have been created exclusively for IBM Cognos Analytics. The Extended Samples require the use of a database and database connections to host the sample Great Outdoors data. They must be installed and configured. Here are the instructions for installing the Extended samples. We have also created a set of Base Samples in a deployment that can be easily imported in one step. These samples exclusively use Data Modules as their underlying data sources (no cubes, databases, or packages). Here is a video that explains how to find and import the Samples_for_Install_11_0_11.zip deployment file. After you import the deployment, you will see the following new Base Samples: Team content > Samples > Reports Storm events 2015 This sample report showcases the new custom polygon and point mapping functionality in the context of storm event data. You can read the full details in this Blog post Team content > Samples > Data Sample data module This sample data has been updated to include a new column for Product Number. SampleFile_GOSales.xls This sample data has been updated to include a new column for Product Number. Storm events 2015 This sample data module has been updated to include a new calculated column for Region (Northeast, Midwest, South, and West). JavaScript Samples The existing IBM Cognos Business Intelligence 10 JavaScript Prompt API samples have been migrated to IBM Cognos Analytics 11. You can read the full details in this Blog post. All of the JavaScript samples now use data modules as their data source, rather than the Sample Outdoors Company database. Related posts: Mapbox hosted custom polygons in reports and dashboards Cognos 10 JavaScript Prompt API samples in IBM Cognos Analytics 11 IBM Knowledge Center: Setting up Mapbox to work with IBM Cognos Analytics IBM Knowledge Center: Using custom point or region information from Mapbox in a map vizualization in a dashboard IBM Knowledge Center: Using custom point or region information from Mapbox in a map visualization in a report Samples landing page Guide to IBM Cognos Analytics sample data sets Library of How-To Videos for IBM Cognos Analytics Please visit our IBM Business Analytics Support channel on YouTube.

Blog

Video: Cognos 10 JavaScript Prompt API samples in IBM #Cognos Analytics 11

Welcome to our video about how the Cognos 10 JavaScript Prompt API samples have evolved in the IBM Cognos Analytics 11 environment. In this video we will show the 10.2.2 Prompt API samples, the equivalent 11.0.11 samples, and demonstrate what has changed. Related posts: Cognos 10 JavaScript Prompt API samples in IBM Cognos Analytics 11 Library of How-To Videos for IBM Cognos Analytics Samples Landing Page Guide to IBM Cognos Analytics sample data sets Please visit our IBM Cognos Analytics channel on YouTube.

Blog

Data caching in dashboards

In continued efforts to ensure Dashboards perform at their best we are introducing the ability to control data caching at the overall dashboard level. You will find Data cache under the properties of the dashboard. The default value is Automatic which picks up the corresponding setting from the data source a widget is connected with. In version 11.0.11 the Automatic setting only applies if you are using a Framework Manager package but it is expected that future versions of Cognos Analytics will support caching properties within data modules. The corresponding setting in Framework Manager is a governor called Allow usage of local cache. The dashboard data cache property also has options to turn it On (cache is used whenever possible) or Off (never cache data). These apply to live connections to data servers within a package or data module but are not applicable to data sets or uploaded files. This data cache contains results from SQL queries to data servers that retrieved the data presented in dashboard widgets. In processing a dashboard widget, the system determines whether the widget is a candidate for reusing cached data. If so, the system will check whether the results for a compatible SQL statement have been cached for the same data server connection. If so, that cached data will be reused. Results that are cached from one user’s dashboard can be reused for a different user’s dashboard only if both users have the same data security profiles. No need to worry about users seeing data that they should not. This cached data is retained in a Cognos Analytics server’s memory for as long as the original connection to the underlying data server remains open. These connections have a default idle timeout of 300 seconds (5 minutes) which can be modified in the Administration console. When the dashboard widget property Refresh Automatically is turned on, data caching won’t occur for that widget no matter what.

Blog

Mapbox hosted custom polygons in reports and dashboards

With Cognos Analytics 11.0.11 users will be able to visualize custom polygons hosted on Mapbox within reports and dashboards! Here’s how you can start visualizing your custom geospatial polygons in Cognos! You can refer to the instructions below or watch the video that shows you how to add custom polygons. If you don’t have a MapBox studio account already the first step would be to create one (each organization/department can host all their polygons on one account). For many of our users the free account with 5GB of storage space should be more than sufficient to host all their polygons. Then upload your geoJSON custom polygon file to Mapbox as a tileset. Custom polygons in different formats such as .shp and .KML can be easily converted to geoJSON using several open-source software (QGIS is recommended). A tile-set is essentially a compiled set of geoJSON optimized to render fast on a browser. If your geoJSON is under 5MB, you will also be able to edit the geoJSON directly in Mapbox-datasets through an intuitive UI. Once edited it can be exported into a tileset. Each polygon will need to have at least one uniquely identifying property (we recommend that this be an abstract identifier) Ensure the tileset is made Public (Tilesets are public by default) Once you have you tileset created in Mapbox you will need 3 keys from the tileset page. 1 – MapID, 2 – Layername, 3 – Property Name (unique identifier)   Mapbox tileset In the Cognos Map visualization expand the properties pane and enter the 3 keys from the step above. This workflow is identical in both Cognos reporting and dashboards. Then simply drag your Property name (unique identifier) into the locations slot and a measure (s) under the location colour/Point colour/point size slot. That’s it!     Note – if your custom polygons are points then enter the 3 keys in the points layer instead. Best practices Do not add any confidential or sensitive information as a polygon property. Although, not common, if your existing geoJSON has sensitive information in its properties, we recommend that you remove them before uploading your polygons to Mapbox. Best practice would be to make the geoJSON property an abstract identifier. Share the 3 keys to your Mapbox tiles on a need-to-know basis. For better performance and to guarantee polygons appearing at zoom level 0 (world view) it is recommended to compress larger geoJSON files to less than 10MB. http://mapshaper.org/ is a fantastic free tool to do this. a. geoJSON larger than 10MB will be set default zoom extents that may not begin at worldview – level 0 (this is a mapbox optimization technique). However, if you want to manually change the zoom extents there are few ways to do so. i. Tippecanoe APIs (Linux, MacOS) ii. Download Mapbox studio classic on your desktop (windows) and change min/max zoom levels iii. Mapbox documentation here: https://www.mapbox.com/help/adjust-tileset-zoom-extent/ To ensure that autozoom works in Cognos reporting we recommend setting the unique polygon identifier as a string value. For those working with custom polygons in small areas (postcode level) we recommend turning off auto zoom after the initial map render. This will result in a better experience when filtering as the map will not have to reset zoom and pan in multiple times. Related posts: New Base Samples for IBM Cognos Analytics 11.0.11 IBM Knowledge Center: Setting up Mapbox to work with IBM Cognos Analytics IBM Knowledge Center: Using custom point or region information from Mapbox in a map vizualization in a dashboard IBM Knowledge Center: Using custom point or region information from Mapbox in a map visualization in a report Please visit our IBM Business Analytics Support channel on YouTube.