Blog

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

Archive Results

Blog

Administration: How to setup a Generic OpenID Namespace against Auth0 with Cognos Analytics 11

The purpose of this blog is to extend the capabilities of the number of supported OpenID Connect Providers with Cognos Analytics to now include the Generic OpenID Identity Provider. This allows the ability to “customize” the configuration based on the Identity Provider of choice not listed. Here we have a real lab example of configuring a Generic OpenID against Auth0: Environment: Windows 2016 Single Installation Cognos Analytics 11.0.11+ Identity Provider: Auth0 Section 1: Steps to creating and configuring an Auth0 application: 1. Create an Auth0 Application by clicking on “CREATE APPLICATION” button 2. Give the application a name e.g. IBMSUPPORT in this case 3. Click on the “Settings” where the ClientID, Client Secret are shown: 4. Scroll down to “Allowed Callback URLs” and add the Cognos Analytics URL 5. Click Save 6. Access the https://manage.auth0.com/#/tenant 7. Set the “Default Directory” to “Username-Password-Authentication” and click “Save” Section 2: Collect all the information required and create a Generic Namespace The following information is required: ClientID Client Secret Redirect URL 8. Download the Issuer Certificate by accessing http://auth0.com   9. Save and transfer over to the Cognos Analytics <install>/bin64 directory 10. Import the certificate using the following command line: <install>\bin>ThirdPartyCertificateTool.bat -i -T -r <certificate> -p NoPassWordSet 11. Launch Cognos Configuration and create a new Generic Namespace:     12. Update only the following details Customize from default values and the following are only required in this case: Discovery Endpoint URL Scope for Authorized Endpoints (default is openid): openid profile email name given_name family_name offline_access Password Grant – Strategy: UserInfo endpoint Username: nickname NB: The settings required for a Generic Template may vary depending on the IdP (Id Provider) and the supported Grant Types and Claims. Also ensuring all URI’s are SSL enabled i.e. switch from http to httpS including the redirect url. 13. Test the Connection   When the “Testing ‘IBMSUPPORT’ namespace” is successful then the imported certificate is trusted. However, the userID/password to test the connection may fail with Status 403 error. To resolve this, disable the “OIDC Conformant” setting as follows: 14. Application - <Application> - Advanced Settings – Oath and Disable the “OIDC Conformant”   15. From that same page select “Grant Types” and unselect “Client Credentials” and select “Passwords” 16. Now, test the connection again and it should succeed 17. Save and start the CA Service 18. Select the Generic Namespace which redirects to the Auth0 Log-In Page:   19. Log in using your email address and then it will redirect back to CA and login seamlessly:   Optional: Check the Namespace is active (IBMSUPPORT) from Manage – Administration - Security Additional Information Create Additional Users: From the Dashboard Select “Users” and then “CREATE USER” button Populate the Email, Password and Repeat Password fields. References: Auth0 Documentation Cognos Analytics OpenID Connect authentication providers Other OpenID Blogs Administration: How to setup #Cognos Analytics OpenID Authentication Proxy federating with Active Directory and LDAP over AD Administration : How to setup ADFS OIDC with #Cognos Analytics Release R9+ Administration: How to setup and authenticate via OIDC OKTA integration with AD on-premise and Cognos Analytics 11 R9+ Administration – How to Setup OpenID Connect using OKTA Identity Provider with #Cognos Analytics Release 8+  

Blog

Creating High Performance Dashboard and Report Using Cognos Data Set

Authors: Kevin Nichols (Performance) and George Xu (Senior Software Developer)   Introduction The project timeline is tight. You need to come up with a reporting solution quickly with high performance. The data set from IBM Cognos Analytics could be your best choice. Building on top of the existing Cognos reporting platform, the new data set feature produces a data snapshot from a package, an external file or even a module. The data set provides on the fly, self-serving ETL capability without the need for a complex ETL tool and related technical expertise. A report/dashboard developer can develop a report/dashboard against a data set using a module, produce much more improved performance because of the high-efficient data storage, simplified query process and better data cache in Cognos data set service. Design Flows The following flow chart demonstrates the possibilities of utilizing this new data set capability. The first scenario delivers dashboard/report via dynamic generated queries directly against the data source, provides near “real time” data reporting. The second scenario delivers much faster performance via data set with a smaller data volume however the data freshness depends on how frequent the data set is built. The data set feature is perfectly designed to the situation when data does change, however in a manageable manner. Performance Comparisons Below is a performance comparison of a report based from a package vs a report based from the same package to a data set from a module. As you can see, first opens have increase by over 85% and subsequent run by over 58% by using this technique. How to Create Data Set Data Set/Module functionality can be used with reports that were based off a package. For creating a data set based from a package we used the following steps: Using a per-existing package, from the ellipsis select “Create data set” from the menu. New Data Set UI New Data set UI will display to the end user. From the source plain, select the desired items (essentially the same items from your report based on the package) you wish to be apart of the data set and drag them to “Add data here” window. This will pre-load the items with data from your reporting data tier, now save and load the data Note: If the contents in which you are loading is more than 100K of rows, it would be best to save and load the data as a background process Data Set Reload To reload the data outside the New data set GUI, select your newly created data set and ellipsis select “Reload” Note: This action will perform a background process data load from your data tier to your newly created data set. Data Set Data Load Through Scheduling As data changes on the data tier you may want to schedule a reload during after hours. By selecting the properties of the data set and selecting the schedule tab then New you can enter a time to best suite your needs Module based on Data Set Now that the data has been loaded into the data set you can create a new module based on the preloaded data set you just created. Select New > Data Module > Data Set Select your data set which was based off your package and select Done Module UI New Data Module UI will now appear. Select and drag the new data set pre-load data based off the package under the new New data module from the Data module plain. Save the newly created Module. Module Report / Dashboard Creation With the newly created Module, you can create a report or a dashboard to display the rows from the report data tier. The benefit of this is that on heavy server based reports, you could gain in performance up to 6 times for first hits and over 2 times with subsequent runs due to the pre-loaded parquet data set data. Summary - Data Set Advantage Empowers self serving capability without traditional ETL and IT development work Produces faster performance with reduced resource requirement to overall system

Blog

Your #Cognos Analytics Cloud Migration - Client Success Webinar Session 2 Replay

Thanks for attending the webinar delivered by the IBM Analytics SaaS Client Success team.  Here is the recording from: Cognos Analytics Session 2 - Your Cognos Analytics Cloud Migration During the second session, we covered: Recommended approaches for your cloud migration Things to consider when upgrading and/or moving to the Cloud Cognos Analytics Roadmap How IBM can help – resources, partners, services [video width="1440" height="768" mp4="https://community.watsonanalytics.com/wp-content/uploads/2017/10/Cognos-Analytics-Session-2-–-Your-Cognos-Analytics-Cloud-Migration-20170927-1635-1.mp4" poster="https://community.watsonanalytics.com/wp-content/uploads/2017/10/Cloud-Migration-Blog-Header.jpg"][/video] Recorded - Wednesday, September 27, 2017 If you would like a copy of the presentation, please contact your Client Success Manager.  In case you missed it, Session #1, "Latest Capabilities of Cognos Analytics" can be viewed here.

Blog

VIDEO: #Cognos Analytics Report Authoring Basics – Part 4: Visualizations

Report Authoring Basics This is a series of short videos aimed at Cognos Analytics Report Authoring beginners. Part 4 - How to create a Visualization Report This video describes some common aspects of creating a Visualization report: Sorting Formatting Color Palettes Labels Titles Legends

Blog

Latest Capabilities of #Cognos Analytics - Client Success Webinar Session 1 Replay

Thanks for attending the webinar delivered by the IBM Analytics SaaS Client Success team.  Here is the recording from: Cognos Analytics Session 1 - Latest Capabilities of Cognos Analytics During the first session, we covered: New capabilities going from Cognos 10 to Cognos Analytics 11 Benefits of moving to the Cloud Demonstrations of the latest features including integration with Watson Analytics [video width="1024" height="768" poster="https://community.watsonanalytics.com/wp-content/uploads/2017/09/Cognos-Blog-1.jpg"][/video] Recorded - Wednesday, September 20, 2017 Session #2, "Your Cognos Analytics Cloud Migration" occurred on September 27, 2017 and the recording is now available.

Blog

Learn what's new in the latest release of #Cognos Analytics 11.0.7

The latest release of Cognos Analytics, R7 is here and I am excited to share the details about all of the new functionality. Cognos Analytics R7 puts more capabilities at your fingertips for working with and analyzing your data, all without leaving the environment. And, creating pixel-perfect, interactive professional reports just got a lot faster. This new release is chock full of new capabilities and enhancements that cover all aspects of the product starting from the improved U.I., to dashboarding, reporting, modeling, data server, and the list goes on. Some of the highlights include capabilities that make it easier for users to use more of the data preparation, data discovery and reporting capabilities with: New, enhanced visualization types with measures as attributes on axis, support for chart values and more Calculation advancements for data modules and dashboards Filtering enhancements that enable you to do more with your filters in both your visualizations and reports Support for maps in your reports for greater readability and precision Navigation enhancements that make it easier for report users to drill down and back to change the focus of their analysis For more details on all of the new capabilities in R7 check out the series of blogs below, and you can access the free trial of Cognos Analytics which has been updated as well: Portal enhancements Dashboarding Storytelling Powerplay Planning Analytics Reporting My Parameters Interactive Performance Assistant Data server updates Data modeling enhancements User Session Logging

Blog

#Cognos Analytics and #Planning Analytics Integration – Walkthrough - Part 2

The integration of Cognos Analytics and Planning Analytics (or Cognos Business Intelligence with Cognos TM1) is often seen as a complex topic, especially when it comes to troubleshooting. This document will provide a walkthrough of the integration between Cognos Analytics and Planning Analytics, and will list regular scenarios and it´s resolution. This integration is often also referred to as “using CAM Security”. This is Part 2 of the Walkthrough, and builds upon Part 1. In Part 1 the tm1s.cfg was adjusted to use IntegratedSecurityMode=5, and TM1Web was configured to use this as well. Part 2 will provide the steps for TM1 Applications and TM1 Operations Console. Just as a short recap, tm1s.cfg has the following content after the changes in Part 1: [TM1S] IntegratedSecurityMode=5 UseSSL=T ServerName=Walkthrough AdminHost=pa-adminhost PortNumber=12346 HTTPPortNumber=8010 DataBaseDirectory=. ServerCAMURI=http://ca-host:9300/p2pd/servlet/dispatch ServerCAMURI=http://ca-host:9400/p2pd/servlet/dispatch ClientCAMURI=http://web-host:80/ibmcognos/bi/v1/disp ServerCAMURIRetryAttempts=2   The Planning Analytics Application Server is assumed to run at http://pa-host:9510. Using IntegratedSecurityMode=5 with TM1 Applications (pmpsvc) Prerequisite: Section Change Security Mode of the TM1 Server of Part 1 needs to be completed prior. Step 1: Configure planning.html Similar to tm1web.html, a configuration file on the Cognos Analytics server needs to be adjusted with the URLs used for Planning Analytics. This configuration is done in planning.html, which has been copied as part of the bi_interop.zip in the first step of the integration. The file is located in the <cognos analytics gateway>\webcontent directory of the Cognos Analytics Gateway installation. The URL that is used to open TM1 Applications Portal, will need to be added to a list of allowed referrers. 1. Open <cognos analytics gateway>\webcontent\planning.html in an editor 2. Search for “var planningServices” 3. Expand the list of URLs from var planningServices= ["http://localhost:8080", "http://localhost:9510"]; to var planningServices= ["http://localhost:8080", "http://localhost:9510", "http://pa-host:9510"]; 4. Copy the changed planning.html to <cognos analytics gateway>\webcontent\bi   Assuming your users would not access TM1 Applications through pa-host, but through pa-host.domain.com or through a proxy (proxy.domain.com), these URLs needs to be added to the list as well. For example:var planningServices=["http://localhost:8080", "http://localhost:9510", "http://pa-host:9510","http://pa-host.domain.com:9510", "http://proxy.domain.com:9510"];   Step 2: Configure the Cognos Analytics URLs in Planning Analytics Applications Portal The configuration of Cognos Analytics needs to be made aware to the TM1 Application Portal. This is done in the initial configuration of TM1 Applications.   1. Open http://pa-host:9510/pmpsvc in a browser 2. Enter the Planning Analytics Server details. The URLs will be pre-populated by the configuration of tm1s.cfg. Correct the URLs if they are not as expected. 3. Select Ok.   This configuration is stored in \webapps\webapps\pmpsvc\WEB-INF\configuration\fpmsvc_config.xml. Step 3: Verify the login in pmpsvc 1. Open http://pa-host:9510/pmpsvc in a browser 2. The Cognos Analytics login screen appears. Enter the credentials of a valid Cognos user, that has access to the TM1 Server 3. Logoff   Step 4: Verify the login in Performance Modeler and Cognos Insight 1. In a browser, open http://pa-host:9510/pmpsvc 2. The Cognos Analytics login screen appears. Enter the credentials of a valid Cognos user, that has TM1ADMIN access. 3. Select the Performance Modeler icon. If Performance Modeler has not been installed before, Performance Modeler will now be installed. 4. Performance Modeler will be opened with your user credentials 5. Close Performance Modeler   Repeat the same for Cognos Insight. Step 5: Integrate TM1 applications in Team Content of Cognos Analytics Cognos Analytics can be configured to contain links to published applications in Planning Analytics. This needs to be configured before the publish happens. In the background URL, objects will be created in a defined folder in Team Content of Cognos Analytics. 1. Open Cognos Configuration of Planning Analytics 2. On the Environment entry, enter the details of the Cognos Analytics environment 3. Save and re-start the IBM Cognos TM1 Service.   Create and publish an application through Performance Modeler afterwards. The applications will be available in Team Content > IBM Cognos TM1 Application – My Applications by default. Common problems during this step of the integration   "The planning service parameter was not specified or is not one of the configured locations” or a white page. Step 1 of this integration has not been performed correctly. Make sure that each URL, on how you access TM1 Application Portal is entered in the <cognos analytics gateway>\webcontent\planning.html and it´s copy <cognos analytics gateway>\webcontent\bi\planning.html.   The file "portal\variables_plan.xml" could not be opened The first step of Part 1 suggested to copy the bi_interop folder into the Cognos Analytics installation, which provides the required variables_plan.xml. The variables_plan.xml needs to be present at <cognos analytics>\templates\ps\portal for every dispatcher.   Team Content of Cognos Analytics is displayed, instead of TM1 Applications Portal The Gateway URL has been incorrectly defined. Open <PA install>\webapps\webapps\pmpsvc\WEB-INF\configuration\fpmsvc_config.xml in an editor, and correct <gateway uri="http://web-host:80/ibmcognos/bi/v1/disp"/> to the proper URL. A restart of the IBM Cognos TM1 Service is required. The header of the TM1 Applications Portal is not displayed, or Performance Modeler or Cognos Insight can´t be opened TM1 Applications is configured to show in Compatibility view in Internet Explorer. Error 404: javax.servlet.ServletException: java.io.FileNotFoundException: SRVE0190E: File not found: /disp This error might be happening when one of the applications is opened in Team Content of Cognos Analytics. This is due to an incorrect URL reference (more information APAR PI79680). To resolve this edit the URL object, and change the beginning of the URL from ./disp to ./v1/disp .   Using IntegratedSecurityMode=5 with TM1 Operations Console (pmhub) Prerequisite: Section Change Security Mode of the TM1 Server of Part 1 needs to be completed prior. Step 1: Configure pmhub.html In addition to the tm1web.html and planning.html configuration, a configuration file also exists for TM1 Operations Console. This configuration is done in pmhub.html, which has been copied as part of the bi_interop.zip in the first step of the integration. The file is located in the <cognos analytics gateway>\webcontent directory of the Cognos Analytics Gateway installation 1. Open <cognos analytics gateway>\webcontent\pmhub.html in an editor 2. Search for “var pmhubURLs” 3. Expand the list of URLs from var pmhubURLs= ["http://localhost:8080", "http://localhost:9510"]; to var pmhubURLs= ["http://localhost:8080", "http://localhost:9510", "http://pa-host:9510"]; 4. Copy the changed pmhub.html to <cognos analytics gateway>\webcontent\bi   Assuming your users would not access TM1 Applications through pa-host, but through pa-host.domain.com or through a proxy (proxy.domain.com), these URLs needs to be added to the list as well. For example:var pmhubURLs=["http://localhost:8080", "http://localhost:9510", "http://pa-host:9510","http://pa-host.domain.com:9510", "http://proxy.domain.com:9510"];   Step 2: Configure TM1 Operations Console TM1 Operations Console is configured in a web interface. This UI presents multiple options of configuration, including the references to the Cognos Analytics environment.   1. Open http://pa-host:9510/pmhub/pm/admin in a browser 2. Expand configurations 3. Select PM Hub-Security 4. Enter the URLs from the Cognos Analytics environment   Step 3: Verify the login in pmhub 1. In a browser, go to http://pa-host:9510/pmhub/pm/opsconsole 2. The Cognos Analytics login screen appears. Enter the credentials of a valid Cognos user, ie. that has TM1ADMIN access. 3. TM1 Operations Console should now be open.   Common problems during this step of the integration   White page being displayed A white login screen can appear after the user credentials have been entered in the Cognos Analytics login window. This happens when step 1 of this integration has not been performed correctly. Make sure that each URL, on how you access TM1 Operations Console is entered in the <cognos analytics gateway>\webcontent\pmhub.html and it´s copy <cognos analytics gateway>\webcontent\bi\pmhub.html.   The file "portal\variables_plan.xml" could not be opened The first step of Part 1 suggested to copy the bi_interop folder into the Cognos Analytics installation, which provides the required variables_plan.xml. The variables_plan.xml needs to be present at <cognos analytics>\templates\ps\portal for every dispatcher.   A loop happening between the Cognos Analytics Gateway and the TM1 Operations Console URL The CAMBIURL has been set to an incorrect value in http://pa-host:9510/pmhub/pm/admin, Section PM Hub-Security.       Stay tuned for the next part covering the Integration between Cogonos Analytics and Planning Analytics for Planning Analytics Workspace and Planning Analytics for Excel

Blog

What's Old Is New: PowerPlay 11.0.0

If the lack of PowerPlay support has held you back from upgrading to Cognos Analytics, now is the time to make the move! With the introduction of PowerPlay 11.0.0 you can now work with all of your PowerPlay content in Cognos Analytics. The 11.0.0 release of the PowerPlay client includes new versions of: PowerPlay Enterprise Server PowerPlay Windows client Transformer The core products are effectively what they were in their 10.2.2 versions, with the following updates: PowerPlay Windows client and Transformer now officially support Windows 10. PowerPlay Studio now supports the following browsers: Chrome 59.0.3071.104 Firefox 54.0 Internet Explorer 11 PowerPlay Enterprise Server now uses Cognos Analytics as its portal. All PowerPlay Windows client and Transformer documentation is now contained within the IBM online Knowledge Center. This is an upgrade for all existing PowerPlay license holders. When you go to Passport Advantage to obtain your copy of PowerPlay or Transformer, be aware that the products are only available via download – physical media is no longer provided for these products. And while we’re talking about upgrading, it is important to let you know that the 10.2.x versions of the PowerPlay products will reach their end of service (EOS) at the same time as IBM Cognos Business Intelligence 10.2.x – April 30, 2018. The same extended support that is available for IBM Cognos Business Intelligence is also available for IBM Cognos PowerPlay. PowerPlay Enterprise Server will continue to be installed separately from Cognos Analytics, and in a different location. Unlike the earlier PowerPlay Enterprise Server 10.2.2 interoperability with Cognos Analytics, the only requirement to configure PowerPlay properly is to update its configuration to point to the Cognos Analytics content store. Once that is done and you have started Cognos Analytics and PowerPlay Server, in that order, you will immediately be able to access PowerPlay Studio from within the Cognos Analytics portal. PowerPlay Studio and PowerPlay PDF report output run in separate browser tabs from the rest of Cognos Analytics. PowerPlay will not necessarily be released at the same frequency as Cognos Analytics, but when it is, it will most often occur in conjunction with a Cognos Analytics release. IBM will ensure that the latest version of Cognos Analytics continues to interoperate properly with the latest version of the PowerPlay products. The IBM-supported software environment site will be updated to contain this information. With the initial release of PowerPlay 11.0.0, you will need to use Cognos Analytics 11.0.7. PowerPlay Enterprise Server continues to support multi-server installations and routing rules as it did in version 10.2.2. Aside from the updated browser support, probably the most exciting thing about the new PowerPlay Enterprise Server is its use of Cognos Analytics as its portal, allowing Cognos 10.2.x customers who use PowerPlay to more easily upgrade to Cognos Analytics. PowerPlay Studio is now launched from the legacy application area, but all of your PowerPlay reports and report views can be executed and managed from within the Cognos Analytics portal. When you save a PowerPlay report, it now appears in the Cognos Analytics portal with its own icon. From within the portal you can perform various actions on the report: As before, you can run a report interactively or in the background, set parameter values, or create a report view. Note that when you set prompt values on a PowerPlay report or report view, the 10.2.2 prompt interface appears in a separate browser tab. Although PowerPlay Studio is integrated with the new Cognos Analytics portal, it is not possible to use interactive reports as drill targets from a PowerPlay report. You can use the Cognos Analytics scheduling feature with PowerPlay report and report views just like you can with other Cognos Analytics reports.

Blog

Portal Enhancements in #Cognos Analytics 11.0.7

In Cognos Analytics 11.0.7 (Release 7), the portal interface has been refined in several ways to both improve the customer experience and cross-pollinate the experience and technology with Watson Analytics. Perhaps the most obvious change is the Welcome screen, where your most recently used items appear as tiles, much like they do in Watson Analytics. These tiles are live; you can click the ellipses to take actions. To provide a more self-supportive environment, we have added Quick Reference Links that provide instant access to getting started videos, sample data and communities. Content navigation has been simplified also. Rather than having two views of the content (expanded and collapsed) the capabilities are integrated into a single view. You can resize the content pane to see long names. You can use the bread crumbs to navigate within the content, and you can sort content in ascending or descending order by name or last modified date. Uploaded files has been moved to the New menu, and Notifications has been moved to the bell icon in the top right corner of the screen. And finally, a great addition near the top left corner of the screen: the home button, which will return you to your home screen in a single click. This is a more direct route to your home page than using the switcher. We have also addressed a very popular Request for Enhancement 100811 (104176): “Do not show Hidden Folders in Cognos Analytics Search.” As of Release 7, if the user preference is set to not show hidden folders they will also not show in the search results. All in all, Release 7 offers a streamlined and improved portal experience for the user.

Blog

Tell stories that resonate with Storytelling enhancements in #Cognos Analytics 11.0.7

This release brings some updates to the playback experience in both the normal view and full screen viewing experience, a new inter-scene transition option and the ability for customers to upload images to create a library for users to leverage in dashboards and storytelling. Playback User Experience enhancements To ensure a consistent view when playing across both the regular and full screen playback, we have updated the playback to be the same across both views. In addition to this we have adjusted the location of certain action and included a progress bar to allow users to easily view their relative place in the scene they are viewing. Animated Path If you have every seen a “videographic” courtesy of website such as the Economist, this transition will be familiar. Animated path allows users to have elements from their story move and/or resize as you transition from one scene to another. The advantage of this is that items can remain on the screen for reference, but be placed off to the side or bottom where they will visible but not the focal point, to help provide context as users progress through a story. In order to obtain this transition you must create a slide show, duplicate the scene, and ensure that the element(s) you want to transition are visible at the end of the first scene and the start of the subsequent scene. Image Library Until 11.0.7 to add images to a dashboard or story a user would need to utilize the image widget and paste in a URL. This posed a few problems where if the image was taken down or blocked the image would be removed from the Cognos asset. The image library utilizes the same underlying capabilities that were exposed in an earlier release for extensions and custom shapes. This requires a user to create a small JSON document providing some attributes to the images and create a zip file with these images and the JSON file. This zip is then uploaded into the Cognos system via the extensions panel (found here: Manage -> Customization -> Extensions). You can have multiple image zip files uploaded so long as the IDs are not duplicated. For more information, please visit this blog post.   If you wish for certain images to only be visible/available to certain users, you can leverage the role customization capability. Here is a short video that demonstrates these new features: