Imagine your organization has decided to update their brand, and you’re tasked with updating the fonts on ALL company-wide reports that aren’t Arial or Helvetica with Arial. But how would you proceed to accomplish this herculean task? The average Cognos customer has between 10,00 and 15,000 reports in their production environment. So you would have to dive into tens of thousands of reports and manually edit each and every one! MotioPI Pro provides a more efficient method for mass updating all your Cognos BI content. Here is a look into how to update your fonts.
IBM Cognos and Motio Best Practices Blog
How to Setup a Gateway for Cognos 11
A question that we very often get asked is this: “Does the Optional Gateway ever become a requirement?"
And the answer is, “Yes!"
One of the most common scenarios where having an Optional Gateway setup becomes mandatory is having single sign-on (SSO) setup. In this blog post I will cover how to setup an Optional Gateway in Cognos Analytics versions 11.0.2 and 11.0.3. Those who have followed IBM’s official document on setting up the Optional Gateway and are having connectivity issues might find this guide useful. IBM seems to have left out a couple of critical steps for setting up the Cognos ISAPI which I will cover towards the end. Let’s start with a background on the architecture.
**Please note, if you are on Cognos version 11.04 and up, the IIS configuration guideline can be found here. And to make this easier, IBM has a small tool you can download here to automate the process.
A common question that keeps getting asked of the MotioPI Support Staff is how to identify IBM Cognos reports, queries, etc. that utilize in-line SQL in their specifications. While most reports leverage a package to access your data warehouse, it is possible for reports to run SQL statements directly against the database, bypassing your package. Let's talk about why it's important to know which reports have embedded SQL.
In some situations employees leave companies and the organization has not fully prepared for their exit. One specific scenario when an employee leaves that causes a great deal of extra work on IBM Cognos administrators involves the ex-employee's scheduled jobs, reports, etc.
Let's say that Ed has configured many scheduled jobs and reports that go out to a number of people, but he has left the company. Shortly after Ed's last day, several of these people are not receiving their scheduled Cognos reports. These employees contact their administrator. The administrator investigates and sees that these specific failed reports are attempting to use Ed's account and since he has left the company, his account in LDAP is inactive, causing the reports to fail.
In IBM Cognos, schedules are associated with a "credential," which is a security token that is associated with a Cognos user. In this case, Ed's schedules execute and authenticate through his credential. His stored credential passes to the authentication source (e.g. LDAP, Active Directory, etc.) to get logged in. After an employee leaves, their account becomes inactive in LDAP, AD, or the like, and all of their many scheduled jobs and reports will fail. The Cognos admin is then tasked with figuring out how to find and then reassign all of the ex-employee's schedules.
In Cognos, there is no easy way to do this. There is no search feature that allows you to find all schedules that use a specific Cognos user's credential.
In the second half of the 2-part series on the importance of Business Intelligence tools, we'll get into how an investment in BI software can prevent the costs associated with turnover and human resource mistakes.
In this 2-part series, the importance of BI tools and their impact from a Human Resources perspective and a Business perspective will be explored. But before we get to the nitty gritty, where does your team fall on IBM’s spectrum of Business Intelligence mastery?
There is often a misconception of the idea of security. Many think security means that your system can’t be hacked, and your personal files are not accessible. Security means that nobody can get your great aunt’s secret banana bread recipe. You can never be too secure, right?
You’ve heard of self-deprecating humor, where the comedian roasts himself -- like when Groucho Marx famously said, “I'd never join a club that would allow a person like me to become a member.” That’s not what we’re talking about here. “Deprecate” may not be a word you use every day, but software companies do.
IBM regularly releases new versions of its business intelligence software platform, IBM Cognos. Companies must upgrade to the latest and greatest version of Cognos in order to reap the benefits of the new features. Upgrading Cognos, however, is not always a simple or smooth process. There are many documents available that outline the Cognos upgrade steps, but the potential for uncertainties during and after an upgrade still exists. Therefore, it's important to have a methodology and tools in place that help reduce these unknown variables and improve the management of the upgrade project.
The following is a condensed excerpt from our white paper that provides a methodology and discusses tools that improve the IBM Cognos upgrade process.
October of 2014 marked IBM’s annual conference for Cognos and a variety of other products, which was formerly known as IBM Information on Demand and now known as IBM Insight. The conference was filled with sessions, hands on labs, guest speakers, booth visits, and much more. Just because you couldn’t attend Insight 2014 in Las Vegas doesn’t mean you should miss out on the key features of the conference. Here are some of the highlights:
The new 10.2.2 release of Cognos Business Intelligence was the topic of many sessions and presentations, not to mention conversations held by Cognos users. Some of the Cognos 10.2.2 changes discussed relate to reporting and administration features, while others relate to things like hardware and software architecture. See Jeff’s post for more about what’s new in Cognos 10.2.2. The beauty of being at the conference is that these changes were discussed in detail, and customers large and small have the opportunity to start planning implementation of new ideas or time to plan for changes to internal Cognos architecture.