One of MotioPI Pro's basic fundamentals is to improve workflows and how administrative tasks are done in IBM Cognos in order to "give time back" to Cognos users. Today's blog will discuss how to improve the workflow around editing Cognos Framework Manager model element names, descriptions, and tooltips. We will demonstrate a MotioPI Pro feature that makes it easy to update the information that business users see- model terminology elements.
IBM Cognos and Motio Best Practices Blog
Creating shortcuts in Cognos is a convenient way to access the information you use frequently. Shortcuts point to Cognos objects such as reports, report views, jobs, folders, and so on. However, when you move objects to new folders/locations within Cognos, the shortcuts that reference them turn into broken links. You would then have to go into Cognos and recreate all of the shortcuts to those objects that were moved.
Or, you could conveniently move the Cognos objects within MotioPI Pro in order to prevent broken shortcuts and avoid the pain of having to recreate them.
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.
If you are a TM1 administrator, you are likely aware of the demand for maintaining efficient memory usage in your Cognos TM1 instance. Imagine this scenario: your Cognos TM1 environment is starting to lag. You know there exists out-dated TM1 objects, but aren’t sure if they are worth deleting. So you decide to delete objects that haven’t been used in a set amount of time, that use up the most memory. How do you determine which objects meet your criteria?
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?
When you need to reconfigure an existing Cognos environment to a use a different external security source (e.g. Active Directory, LDAP, etc), there are a handful of approaches you can take. I like to call them, "The Good, the Bad, and the Ugly." Before we explore these Good, Bad, and Ugly approaches, let's take a look at some common scenarios that tend to drive authentication namespace changes in a Cognos environment.
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.