Power Pair: Cognos with Power BI or Tableau

Great pairings take two strong standalones and make them even better together. Take wine and cheese. Beer and brats. Peanut butter and jelly. 

What’s a great BI pairing? Cognos plus Power BI and/or Tableau. But…given the tools don’t naturally integrate, organizations run them independently and it’s costing them reporting time and accuracy. 

Learn how the Senturus Analytics Connector allows Power BI and Tableau to easily tap the secure, curated data in Cognos. It’s a powerful pairing both IT and business users can appreciate. 

In this Analytics Connector demo learn about 

  • Simple drag and drop functionality that eliminates time-consuming data remodeling efforts. 
  • How the Analytics Connector results in improved security, data accuracy and overall Power BI/Tableau performance. 
  • The features in our new 5.2 release that further reduce query waiting times and boost performance. 


Pedro Ining
Principle BI Analytics Architect
Senturus, Inc.

Pedro brings over 20 years of BI and data warehousing experience to his role. He has been instrumental in implementing data warehousing systems from scratch and has experienced the evolution of the BI industry through several iterations of BI products including Cognos, Power BI, Tableau and MicroStrategy.

Questions log

Q: Which Cognos license is needed for the Senturus Analytics Connector if we have multiple Tableau users?
A: The old Cognos Report Author license is required because we generate report specs on the fly to get data from Cognos.

Q: Does the Senturus Analytics Connector work with Cognos hosted by any cloud provider as well as on-premises?
A: Yes, the Senturus Analytics Connector works for both on-premises and on the cloud, we get data via Cognos dispatcher.

Q: After I publish a Power BI dashboard, can everyone who uses Power BI workspace access it? Or do they also need the access to Cognos packages?
A: It depends on how you set up a Power BI data source on the gateway. You can use Windows authentication pass through or use your designated log in credential.

Q: For each Tableau user license do we need an additional Cognos Report Author license to use the Senturus Analytics Connector?
A: Tableau users can share a Cognos login with an Author License. Then Tableau users only need a Consumer license.

Q: What Cognos roles are required to use the Senturus Analytics Connector?
A: In Cognos 11, Analytics User or higher role is required.

Q: When using the Senturus Analytics Connector, when do we pair Power BI or Tableau with Cognos other than for visualization knowing that governed data is rendered to PowerBI or Tableau?
A: The Sentrus Analytics Connector actually pulls metadata from Cognos and presents it as a SQL Server database and parses your SQL query and query Cognos data on your behalf. You can use all Cognos reporting features, e.g., row-level security.

Q: Can we use routing rules and divert the load to specific Cognos application servers when we use the Senturus Analytics Connector?
A: The Senturus Analytics Connector connects to a Cognos dispatcher, and Cognos dispatcher will directly request to CM/Report dispatchers based on Cognos load balance rule and/or Cognos routing rules.

Q: Can the Senturus Analytics Connector connect to the oracle database?
A: The Senturus Analytics Connector connects to Framework Manager packages and/or data modules on the Cognos BI server. The Senturus Analytics Connector does not connect to your reporting database directly.

Machine transcript

Welcome to today’s Senturus webinar on the power of pairing of Cognos with Power BI. Thanks for joining us today.

It’s always great to have everybody here. A few quick housekeeping items before we get started. Your GoToWebinar control panel you’ll see a few sections there and the control panel, particularly the questions and chat section for the questions section as we go through the webinar today. You can submit questions in real-time.

We will try to answer some of those as we’re running along, but there will also be a Q&A session at the end of today’s presentation and if we’re not able to get to your question during the actual presentation today, we will be answering those questions and sending out a summary after the webinar.

So, any questions that you have that come up during presentation, just go ahead and type them into the questions panel on the webinar controls.

To obtain a copy of today’s presentation, you’ll find it on the Senturus website. Just go to Senturus.com/resources and you can download a copy of the slide deck.

In terms of today’s agenda, we’ll start, just with some quick introductions of today’s presenter. Will do an overview of the Senturus Analytics Connector, which allows you to connect Power BI and Tableau to your Cognos data.

We’ll do some demos because the Connector in action will cover a list frequently asked questions about the Connector. So by that time, some of the questions you put in the panel may be covered in that section already. We’ll do a little overview of Senturus and guide you to where you can find some additional resources on our website.

For the presentation today, our main presenter is Pedro Ining, Principal Analytics Architect here Senturus. Like many of our consultants he has been in the Cognos space for a long time, pretty much from the very beginning. So Pedro has lots to bring to the table. He’ll be giving our presentation today. I’m Steve, Director of Enterprise Architecture and Engineering. As usual, I’m just doing that kind of talking at the beginning. And Pedro will be the real expert for details.

Before we get started, I want to do a couple of quick polls to get a sense of where you are in terms of the AI platforms that you’re using in your organization. So the first poll is what platforms do you currently use? I’m going to go ahead and start that. You can select one or more of the choices. And probably most of you, at least are using Cognos.

Yep, so, I’m seeing so far, 92% Cognos and, so far about 35%, Power BI, 35% Tableau.

I’ll just keep this open a little longer to give you time to submit your answers.

But it does look like pretty evenly split today between folks who are bringing in Power BI and folks who are bringing in Tableau into their environments.

I’m going to go ahead and just leave this open for a few more seconds for anybody who wants to get their entries in there. We’ll go ahead and close that out.

Just share the results of that real quickly so, as expected, most of you already have Cognos. And, again, it looks like about a third of you are using Power BI in your organization..

About a third using Tableau. So, we’ll be talking a little bit about both of those platforms, of course, in terms of accessing Cognos data through the Analytics Connector.

I’m going to do one more poll here, before I turn things over to Pedro.

This one is how large is the user community for Tableau or Power BI in your organization.

I’m going to go ahead and store data on that and I’ll give everybody a little bit of time to go ahead and submit here, entries there. We do find that it’s generally a subset of the overall Cognos user base that is using Power BI or Tableau.

I just wanted to get a sense of the size of your utilization of those tools.

So, far, it looks actually about evenly split between all of these options. Little more than a third of you, have less than 50 users.

About 25%. Each of the other categories.

I’m going to go ahead and leave this running for a few more seconds.

It looks like most of you have already voted.

So again, it looks like a little over a third of you have less than 50 folks using Tableau or Power BI.

About a quarter of you are in the range of 51 to 250. And even a fifth of you have more than 250, using these newer platforms.

So with that, I’m going to go ahead and turn it over to Pedro for the presentation.

Thanks, Dave. Just the audio check. Welcome, everybody for the overview to Senturus Analytics Connector.

Before we get into that, let’s get a little background information on what’s driving this product in a sense.

Bimodal BI, I think some of you have heard this term, this notion of bimodal BI was termed by Gartner. We’re back in 2015 that didn’t seem that long ago. But I guess it’s pushing seven years on this but back then the BI vendors, the big ones like Cognos, MicroStrategy, Business Objects, those big vendors are really trying to be the single source of truth. All things for everything. And they wanted to be or report writing tool. They wanted to be exploratory approach, wanted to dashboards and things like that.

But, with the advent of Tableau and Power BI, these products tend to be categorized as a mode two, exploratory tool.

So what Gardner was beginning to ask was, do you have two modes of BI in your organization?

And if you look at the mode, one gear, it’s predictable, in the sense that the gears are very well spaced out, they have same amount of length.

Where mode to, it tends to be more exploratory.

You know, in terms of experimental solve, new problems, which is very spikey, right? So, that’s what that graph is showing for two modes of BI.

And, they’re asking, what kind of modes are in the organization because, Tableau and Power BI began descending on people’s desktops.

A lot of times circumventing IT and landing and the finance desktops and finance was asking, IT can have access to tables or I got spreadsheets and things like that.

So it’s a very fast, very agile type of exploratory kind of BI, getting away from the more single source of the truth, very SDLC type environments that Cognos is probably known more for at the time.

So the bimodal approach is definitely growing.

And when they did some surveys, back then, back in 2016, they dismissed surveys up there, who’s doing bimodal approaches of BI.

That’s almost 40% of the organizations, what we’re already doing, bimodal type of analysis.

Then by 2017, that actually grew significantly again by 5%. So we’re all in 2017.

You know, five years ago, We’re already at 50% of a bimodal type of approach in the organizations, right? And now, we’re at 2022. So we’re probably haven’t had any updated numbers on this, But probably very, it has grown very significantly in terms of bimodal approach.

But the one thing about this approach is that the companies who really use there, they’re BI assets. And have a very analytical approach through data appear to be performing better.

And that’s a top performer, in terms of the company themselves, OK? The companies that leverage their data outperform their competitors.

And they do that effectively with the right tool for the job. And even if that includes multiple tools, so that could be Cognos as a certain amount of Power BI. And you sort of tout Tableau.

They actually have maybe all three of these things in place.

And so, what does this have to do with the Senturus Analytics Connector, which we’re going to demonstrate today?

Well, you know, there’s a lot of value that really exist in the existing current BI models that Cognos may have. You know, so, you Cognos folks, obviously recognizes screenshot, as a screenshot from Framework Manager. And, the tool allow you to model complex data into a user friendly format, dimensions and measures, right?

And, these Framework models often took a very long time to create lots of investment, lots of dollars, lots of human capital.

Lots of business knowledge went into these models, and they generally work fairly well, but, then, with the challenge was now with the advent of the more BI mode to exploratory tools like Tableau and Power BI. You know, they had no access to those curated Cognos data models.

Know, these models had very complex business logic, And this is really a very busy slide just to show you, that, even, if you went to the newer data modules, will just showing over here, you have outliers going everywhere, right?

And you have the complexity of the Framework Managed model, shown there, as well, right?

So, how do we leverage that? That’s already in there, do the Cognos, Power BI and Tableau folks have model these things.

How do we do that?

Sometimes, what they’ve been doing is leveraging these things. But, in a sense, using it as a way of circumvention, right? So, what do they do?

They use Cognos as a fancy ETL tool to extract the data into Excel or CSV files.

We’re using Tableau and Power BI, so, yeah, we’re leveraging those FM models. I’m going to create a report.

I’m going to create a nice long, 30 column, Tabular Report, extract it, and then bring it into Power BI and Excel. That’s what I want to do. I want to see all my financials. I want to see my HR data. I want to see my orders.

Sure, you’re not going to give me an access database but Cognos as access to it through the data models. I’m going to put an extra, right? So, sometimes we have seen Cognos clients out there where their top five reports from an audit perspective are really large CSV dumps.

They’re used to extract data into these newer tools.

So what we have here is a potential are very large data compliance issues. You know, you take data out, you circumvents security, maybe you have an admin, take the data out.

And it gets distributed in Excel CSV.

The admin actually takes up removes all security from it. So, maybe, that user shouldn’t see that region, but he’s seeing it, right?

So, the other option is, then, to recreate the model in Tableau and Power BI, Right? So, if you don’t, you do this method, you give access to people to the database behind Cognos.

But, then, you have thousands of tables you might have to model, which could be a major challenge, and it could be doing this.

They could be doing it wrong, and it’s very possible that the highly likely they’re going to be doing it wrong. And it’s very redundant.

So, again, why you shouldn’t try to recreate this metadata. There’s four big areas, time consuming, in a sense that you’ve got multiple metadata layers now in different systems. So, you’ve got the metadata layer in Cognos Framework  Manager. You have a new one in Tableau and N number of Power BI models, because self contained in that sense, your security, your data security is gone  with flat file extracts. You know, that’s basically that’s it. That’s a given. And if you have an admin extract data, Excel, there’s no security there anymore. You have data silos. Back to data silos. When you remodel the data, there could be an error, is one of those data silos that’s getting propagated throughout the organization. They’re looking at different numbers, so, you’re farther  away, from a single source of truth, right?

This really circumvents the single source of truth.

So, the strength of a Tableau, Power BI has all sorts weakness, it allows users to create fast analytics, but it might create end user data models that could yield different answers, right? So, what’s one solution to this? The Senturus Analytics Connector.

So, Senturus saw an opportunity to create the Analytics Connector to leverage all the rich legacy metadata layers that exist in Cognos so that you can get access to that high quality data that’s been there for a long time.

So, what we’re showing here, for example, is a screenshot of Power BI connecting to our Connector, it looks like a SQL Server database, and, on the right, you see Tableau.

So, you have instant access to quality datasets.

Here, this is really showing you, Tableau.

If you look on the left, you see the common interface of Cognos.

That’s basically Cognos trying to query against the gold sales query subject area and, actually, what happens now when you bring it into Tableau via the Connector.

You can see the correlation from the sales table and all those tables, those namespaces.

Those queries Subjects’ now map to basically tables N in Tableau itself.

And you could also use Cognos reports through the Connector as a source of data.

It can use these predefined reports, because you’ve probably seen actually reports that have additional logic above and beyond the Framework model.

You’ve probably seen very complex reports in Cognos with multiple sub queries and joins and unions to get the final answer.

And maybe they’re actually run in the background, they’re actually very good. Report surveyor reports have been around for a long time.

And actually, to recreate that logic, and maybe that Tableau might be very time consuming as well, you could maybe leverage these reports as a very simple flat source. But instead of extracting it, you actually point to the report that has all that logic and bring it into Tableau.

So, this is logic that’s in the report that maybe, has yet to be pushed upstream to the FM model or the data or house tables yet.

So this is another way that you could potentially use the Connector.

So, basically, you don’t want to sacrifice integrity and security for agility.

You want a little bit of both, right? You want the great visualizations, interactivity. Maybe users have spreadsheets, they need to integrate into their Tableau and Power BI.

But when they’re getting back to those corporate data sources, you know, sacrificing integrity of security fragility might get you into trouble, right?

So you could use the Connector to publish and deploy.

So, once we create Tableau, and Power BI with visualizations and models off the Connector, we can also then deploy that up to the Power BI service.

We could deploy it to the Tableau server as well and still be connected to our Cognos data sources for the FM package.

So, in summary, instead of all the risks, pulling a flat files and other methods to do your visualizations in Tableau and Power BI, the Senturus Analytics Connector gives you a much more faster, more accurate reporting environment reduces change management cost and risk.

Instead of all the changes happening in five different places, you do it in one place, and FM, and it propagates through increased trust in data.

Because the data source from that governed, curated data and Cognos are ready and improved security. So, when you go through the Connector, for example, your user may have to login with their Cognos ID. So, when they actually pull data across, if, you’ve got very complicated, row-level security or roles and Cognos or a baked in Connector, is going to respect that.

So, whatever visualizations they create, if it has, if they only have access to a particular region, or product line, the Connector will expect that kind of security.

And they only get the data, they’re supposed to see.

Superior performance.

This is trying to say that usually the FM model has already been occupied optimized for performance. The joints had been vetted.

Whatever issues, initially, when the FM model was created, has already been vetted and fixed.

But when you have folks going wrong against database tables, and they’re doing the joins, there’s going to be a lot of pitfalls of poorly model data.

So, you’re going to really have that performance baked in or in FM models that are already are working very well, out there, in the organization itself.

So, we’re at now version 5.2. These are some of the highlights of what’s been changed and updated for the Connector. We now have connectivity using Power BI, using the built-in SQL Server connection options.

And there’s no additional client side software that has to be installed on desktops generally. The Connector’s installed on another server. It looks like a SQL Server connection to the users and they login as such, but you actually logging into the connected into Cognos. Power BI gateway support allows Power BI service publish reports and datasets to access on-prem Cognos data.

So, although you’re publishing the reports and connections up to the Power BI service, it’ll go through gateway that could be configured to access your Cognos incident, which is on-premise. So, you have the Power BI service in the cloud. You have your Cognos data on premise.

You go through the gateway, and you can get to it that way.

Power BI report server support.

This allows your Power BI workbooks to be published to a local Power BI report server and then also access on-prem Cognos data.

We now have the ability to leverage Windows integration authentication via kerberos.

So, if you log into your Windows, the main current user credentials can now be passed seamlessly between Power BI, Analytics Connector, and Cognos without prompting you, say, for a Cognos ID.

We have other some other miscellaneous performance enhancements, like, enhance data caching, more efficient connection pooling, the memory usage, and faster handling.

Power BI and Tableau data sampling queries there, where you have to go out and get some samples of data as you model, OK?

So, we’re going to go into a little demo right now, and please bear with me. This is going to be a live demo. We’re going to actually do stuff live. We have our environment where we’re going to actually connect to and show you how this stuff works.

And demos always have a way of going a little crazy, but we’re going to try our best over here.

So I’m basically going to go into a RDP session on one of our zero servers up there.

And I already have Power BI fired up here. So, generally, this is the first screen you’ll see in Power BI. And one of the things you first want to do is, you need to get some data, right? So I’m going to say, Click Get Data here.

And what’s going to be presented to me is a screen.

I want to get data. Now, our preferred connection now, by default, is actually two.

Use a SQL server database connection here.

So the users don’t know it’s a Connector or why they should go to SQL server database. You say Connect.

OK, and then, what’s going to happen is, it’s going to ask, well, what’s the SQL server database server?

What I’m going to do is just actually point to a server. Where are Connectors installed.

And we’re going to go with the Direct Query Mode and say, OK.

My credentials are already kind of cash, but we could, if the kind of credentials were cleared, it will actually prompt you for your user ID password If it’s if that’s the method you’re using to get into Cognos?

What you’re seeing right now, actually, are the packages, or data modules or cubes that have been exposed by our Connector software to be actually used by Power BI?

What I’m trying to say there is, that, actually, if I just bring this screen over here, you may have a whole bunch of packages, like go query, sales analysis, these things have been exposed to what this was.

This is the packages that are going to be shown here.

Depending on what you want to expose to actually connecting, for example, go relational is actually wanting to go, sit, go, sales query, or go query, right. So, it’s like, it’s a direct connection to this package over here on the Cognos lamp.

So, I’m going to go and expand Go relational.

It’s, actually, now, this package has disease query subjects’ exposed.

I’m going to actually click on branch, I want order method.

I want products, I want sales, and I need a time dimension, right?

So, these are the typical kind of things that we want to expose and again, this is actually going ahead and querying the FM package. It’s getting the metadata.

As you can see here, it’s trying to figure out what all the columns are, what their data types are, creating a connection to the model. All going through our Connector. OK, it says, it’s done right now. I’m going to go to the model section right here.

Here we go.

What we have now is, what looks like tables, I’ve got one over here, and I got one over here.

Here we go.

These are actually the tables that are in that FM package.

This is the metadata that we have, so maybe a year FM model. The branch underneath could be a modeling of four tables, right, that’s all handled for you and FM model. You’ve done all that ahead of time that goes sales.

This could be maybe behind the scenes for tables as well, or maybe even more, depending on what? The complexity of what you’re modelling. So there’s a little bit of one little step we have to do here. In Power BI, we actually have to kind of join these things there are already joined, and they have to model and assess what we got.

This sounds kind of fake Power BI to know that these things are joined. What the Connector does is create a AAA link filled.

And what we have to do is just join into the fact. So all we have to do here is put that on top of AAA link, and we see that the branch is going to be joined to the sales via this, these two fields.

You going to make sure it’s a one to many relationship, assume referential integrity, and say.

Now we have a joint. We’re going to quickly go ahead and do that over here.

I’m going to grab this guy.

Come on, grab it. Here we go.

The same thing over here, AAA link.

And always check this cardinality, I think possibly I tries to make a guess at it, but we know us.

It’s a one to many.

It’s a one to many from dimension to fact, assume referential integrity, OK.

There’s another one, and we’ll go, click here to AAA link here, whaling time to sales.

It’s reading it, OK.

And we’ll go on than any assume referential integrity, say, OK.

And one more.

We build products, too, over here, OK, AAA length, AAA link, and make that one of many and assume referential integrity, and say, OK, one-time deal, you’re done, OK.

So, doing this versus OK, going to a database, and seeing 30 tables, that I have to figure out how to make branch work, 30 tables that I have, products, and maybe I don’t do the joins rioted against those, maybe 10 tables that have makeup products.

It’s already done for you, and for model building, I have to do is do this one little step here, Connect them, OK. So Once I’ve got to connect, and I’ve got a live connection to the connector to the package, which now connected to a database, Right, There’s that kind of chain of events.

I’ll go over here to my two visualization area. I’m going to create some visualizations.

I’m going to go over here and move this a little bit so we can get some view. Here’s all the tables, right?

I’m going to go in, Go ahead and click on the country.

That’s automatically going to create kind of a map visualization, and then I’m going up click on a revenue map.

OK, so now, you can see it being rendered over here. So what it’s doing is, remember, we did live query?

So we’re actually getting data through cargo’s to render these values here on the map, right?

So this is revenue for North America is showing you right there, OK?

Let’s create another visualization And we’re going to use the matrix visualization over here.

Oh, one thing I always forget is to make sure you click off.

Click off of that, and then click on that to get this matrix visualization.

So what we could do, it’s also go to our product dimension and create a hierarchy.

So if I go Product Line, Create Hierarchy, I got a hierarchy that I can create, all right, and there’s a hierarchy, And I’m going to add Product Type two, that hierarchy is the way Power BI does it.

OK, and we could even go one level lower, or we could add Product, two here.

OK, so here’s our hierarchy, and I’m going to add my visualization selected.

So I’m going to add Product line hierarchy to this matrix review over here.

OK, and then I’m going to select Revenue, and Plan Revenue.

So, now we have this interactive hierarchy drill data we have using a Power BI visualization where you can see and interact with the actual visualization again.

This is submitting the query through the connector through the FM package through Cognos to get this data OK and cross filtering as enabled. So happy.

Click on this you can see the numbers change over here click off and on the graph. All leveraging.

Nice Power BI if you will but then accessing a leveraging Cognos data. We’re going to do another one here.

We’re going to drag a line chart over here and then we’re going to go over to our Time area, and we’re going to drag the year to the Axis, OK.

We’re going to add Order method type here.

To the legend, and we’re going to add Quantity to the Values.

So now we have a nice little line graph, again, as it’s fetching the data back from Cognos and a little rendering, this graph over here.

And, of course, then, like with any visualization tool.

I know from my experience, you know, maybe it’s 30% of getting the data, then, the next 70% is really making it look pretty by positioning it during the formatting, etcetera. We could add a slicer. We’re going to click Slicer.

Let us get I’d always do this. I’m going to undo that again. Take that back.

Click off, we’re going to go Slicer.

And we want to slice by year.

Slides are there. And so we have a nice slicer.

So, now we can change this over here and leverage that.

And then, of course, we would save our Power BI desktop.

No, save it as, then put it somewhere, you know?

Yes, DB you know, save.

And when you’re ready, you can publish this guy up to your Power BI service, right.

Not going to do this for the interest of time, but you are generally subscribed to a Power BI Service.com, put it in a gestation.

I want all the connection information is already stored is going to go through the gateway.

It’s going to go to the Connector, as code could get going to go. Your users can if they’re just using desktop can stop right here. There’s no other software on their desktop. I’ve connected to, what they think is a SQL server database.

But, it’s basically connecting to a connector server, going through that exposed go sales package and leveraging everything I have here.

So, what you saw there was done in a few minutes leveraging the Cognos package, OK, so, let’s go to Tableau, so, the Tableau side of the house. I’m going to close Power BI down. I’m going to bring up my Tableau.

And, show you that a little bit the differences for that.

OK, again, same thing for them.

We want to connected data. Power BI wants to get data, Tableau wants to connect the data. We’re going to click the Microsoft SQL Server. There’s my server again, internal being one, OK? As asking for a specific username and password, now we do support Windows authentication.

Now, If that’s what you can click that when we don’t have the, main system set up over here. So, I’m going to go over here, I do have a password over here, and click the copying and I had it before you guys see it. So I’m going to go paste.

And I’m, I’m logging now, into the connector this way, which to, to you just looks like SQL Server, it says Select database.

And, again, what this means is, select the package, right.

These are the packages that I have exposed and my configuration that they can get to you from the connector. I’m going to go with, go relational.

Again, It looks very much like what Power BI was doing, right?

So then, I’m going to double click on my fact table sales, adds it to here.

I’m going to just go into this schema area. I’ve got one table.

I’m going to go ahead and click branch to add it in.

And you notice it actually knows the joint.

OK, that’s the main difference between how the connector works with Power BI and Tableau, that AAA link.

It infers that join if you actually click on this you can see it, AAA linked a AAA link. And then, that’s how it knows how to do to join.

But, behind the scenes, Cognos already knows how to join beneath the presentation layer and FM on the Cognos area.

But we were, kind of faking this out, again, so that Tableau can do this join.

We’re going to click on Order method, We’re going to click on Products.

And we’re going to click the Time Query.

All right, and now that I’ve done my modeling, OK, I’m going to go to my sheet and one of the monarch cleanup we have to do, and the just a one-time deal, right? So we’ve got all these tables.

And then this happens with every time you point table to new data source, right? It doesn’t, it’s best. Yeah, what to determine what a dimension is and measure names. So everything below this is measured, and that basically sees some of these dimension attributes that are in these dimensions width is, given the fact that they are numbers, they’re declared as measures well, we don’t want that.

We want to put those back in the dimension area. So we’re going to kind of click through these guys.

We don’t want, we want this to be.

And these are all going to be dimensions.

We’re going to drag it up here, that the dimensions area, and there’s the time and the time, we want to do that, as well.

I’m going to put it up here.

There’s a dimension area, OK, so now we’ve got a nice cleaner look.

And this is from the sales table, and those are facts. So we’re going to leave that there and one other little modern cleanup that we’d like to do is to hide that AAA link field, right.

Those are something that our connector does for Cognos to join two tables together, within Tableau, to respect the join that’s over there and FM side. We don’t have to have the users know about that.

We’re just going to go in here and hide it, so we click on Hide.

And I that one time, they’ll say this. Now, you’ve got, basically, the model that’s an FM.

You got your sales query subject.

You have your dimensions over here, OK? So let us create some visualizations on that.

What I’m going to do is, let’s see, we’re going to go to Branch.

We’re going to double click country.

OK, and as your map right away, we’re going to go ahead now and add the revenue to the Size area, and we’re going to put the profit on the colour.

And, we’re going to go ahead and

Make this size a little bigger.

OK, there you go.

OK, again, live for actually gone back, just like Power BI. Same thing.

We’re going through that connection and retrieving the data to generate this is, but we’re leveraging tableaus, nice visualization features, right, but using clean governed data through Cognos.

OK, so, I’m going to go here, another one, Are we going to use the show me feature within Tableau? We are going to go here to order Method.

The order Method Table, We’re going to click on this, and we’re going to click on Plan Revenue and Revenue.

We’re going to click on the bullet chart, OK. Now said I have a bullet chart.

Again, it’s grabbing the data back. Rendering and here in Tableau will go and create another Visualization for Time series.

We’re going to go to here on the date we’re bringing in a date to the comps.

Now, Tableau has a very nice way of dealing with dates and rolls everything out.

It creates a nice hierarchy for you here, for the day. So, we’re leveraging that.

We’re going to add the Product line, two.

The color side of the house.

And, we’re going quantity on the rows.

OK, so, we have this line graph now.

And, we want to make it more of a continuous, so, it’s on one graph and maybe we want to so, here’s all the nice bits and features that Tableau does. Once you drag a date field in the columns, it knows how to parse that down and we want to make it by month.

So, now, we have a time series analysis done, again, Cognos data. Then, we’ll just go ahead and create a dashboard.

So those of you who do Tableau knows, very well, sheet, and over here, we’ll put the blood chart over here, will next to that, will put our nice little line. OK, so I’ve created a nice, very simple dashboard.

I created three sheets, worksheets, create a dashboard, and again, we could go ahead and save this off as something local to our Tableau Desktop.

And save.

OK, and we’re done, then to distribute to the organization, what we can do is go here to server, and publish the workbook to year tableau Server, So if we publish Workbook, say Connect.

I’m going to put a default folder, we’ll call this Pedro’s connector.

Bring one, for example, and here’s the key thing.

Here in data sources, what we can do is edit this and what we could do is embed the data source in the workbook or publish it separately.

You publish a separately, you have a separate data source of Tableau that, you can create other workbooks offer. So, if we say this, we could publish separately, you will have two entries up to you have the workbook, and then you’ll have the data source. And authentication is an important one.

You have prompt user, or embedded password.

The user comes in handy, because then, if you do prompt the user every time, because you might have a row level security type situation on the cargo side, you want to make sure they don’t, they get the data they’re supposed to, Especially if every level security, so, that’s critical to you.

You click on Prompt User, and every time they run that workbook, then, they ought to be prompted.

And, then, Tableau will get data from Cognos that has respected the user’s ID and only return the data that Cognos says, You can get to.

You can click embedded password, which might be a generic password, like, I’m using.

And, when you put it up there, that’s the password. It’ll use, maybe that’s OK. And then when you run the visualization, then it’ll go up there and then you can say, Publish.

This has already saved their, say yes.

And it’ll go up into there, and this might take a couple of seconds and we’ll get to it.

But, it’s executing a query, is going up the Tableau server, that’s publishing the views.

Sending the data, And then, publishing complete, So, you can see that there’s the data source.

It’s a Connector.

OK, here’s where it is, and if I click on Dashboard, let’s see, if this thing renders might take a couple of seconds.

So, it’s going to basically leverage that data source connection that we have then go through the live connection back into Cognos.

Rendering, There we go, OK.

Here we go.

So, that’s basically the Dashboard you have here.

Again, a live connection, OK?

So if you actually go back to default, let’s do modified, source.

Here’s that connection, you go into here, actually have other connected workbooks. So, I had some connected work, because already as I was preparing for this, all these guys are basically using the same data source, which is a live connection.

All right?

Ah, that’s our demo in terms of what we’re going to show. So I’m going to go back to the slide deck at this point.

And, of course, the slide deck went back to the title slides. I’m going to go back to my demo area.

Did you Know, right here, OK, hold on a second.

Little screen, display, and swap.

OK, so we did the demo Let’s do some frequently asked questions.

OK, so in terms of live, direct query, extract, import and these are terminologies that Tableau is basically the same thing, Says, live, was what I showed you.

Power BI talks about direct query, Tableau talks about it in the context of live. That’s all basically meaning.

If I set up a live or direct query workbook, I’m basically submitting query requests through the Connector, to the FM packets, to the database.

And it’s waiting for the results to come back and pass it back to the workbook.

And Tableau is called Live, and in Power BI is called Direct Query. So, we support that.

We also support extract import which means Tableau comes extracts Power BI calls imports, what you can do and we have actually used this use case for our current client.

Maybe you don’t want live query. Maybe you’ve got a data set out there.

Maybe, you’re leveraging that really cool data module dataset, features of Cognos, right? And I don’t want to query all a database all the time live, right?

You can point this thing to a data module, which might have a nice, very flat, very well defined dataset for a dashboard you want to use in Tableau, for example.

You could point to that, model it, publish the data source up into Tableau and make it an extract.

And, as long as that data source is very well defined, it’ll extract all the data And then, lay it down.

You tell the server in its native hyper file format, OK.

And then, all the workbooks and dashboards that Tableau creates against that high profile are very fast as leveraging that very fast format.

The trick is you didn’t have to try to model your data again to get that extract.

Maybe that data extract or dataset in Cognos land is very complex for whatever reason.

But I’m just getting 30 columns, I’m getting a million rows, but it’s now living in Tableau or very fast, high profile extract. Same thing with Power BI. So, we support both, depending on your use case, depending on what you want to do. You might want to talk about, you know, I want to leverage the hyper file format in Tableau. I want to, I want to leverage the extract format and Power BI, but, how do I get to the data warehouse?

Well, you can go through Cognos: OK, so, I just said, I demonstrate it for you, live query, but you can also do this from an extract, An important perspective in Power BI.

That’s something to think about, something that We’ve actually started to use a little bit out there in the field, and it’s a very good way of doing things, because what we found out, is, like, Tableau users might have written very complex, 2 to 3 page SQL statements embedded as a data source to change that all the time or to figure out what it was doing, was very complex.

We leveraged the Connector, two levers are very well known framework manager model to create that. Support Cognos platforms and versions, obviously support 10 and the whole 11 suite out there right now, latest release of the 11 to 11.2. We up your support on premise and cloud Cognos platforms.

Supported data sources from Congress relational, which I just showed, Power Cubes. Sport that DMR, if anybody’s using the framework manager, GMR mode and we support that dynamic cubes.

If anybody’s use that one, TM1, OK, Framework Packages, and, of course, for those of you that are really working with the newer data modules, I think that’s a really cool way to get the data models. We support the datasets herself, You can’t get directly to datasets.

You had to put the datasets, and data modules was not a big deal, so you can create a dataset and put them into the modules. We support connecting through Data Module to get to those datasets.

And reports, which we talked about, which might have very complex reports that have a lot of logic in them.

You want to leverage that as a source, to get to the data to put in your Tableau and Power BI.

Ah, when did we release this product? Well, it’s actually been out for a while now. We had general release back in November 7, 2016, has been in development now, For over six years. Our current version, which we talked about now, is at version 5.2.

It’s a very lightweight footprint piece of software.

As you can see here, maybe a small box of a gigabytes of ram, Nigel’s CPU utilization has put it on a different server with other things, but, if it sits in a server, basically, you connect to it and then it connects to your Cognos instance.

Supported versions of Power BI. June 2018 or later Tableau Desktop, Tableau Server Tableau Online version 10 or later. There are various flavors of Windows operating systems.

We do support Tableau, Tableau, Linux, Linux, and Tableau Desktop Mac OS of 10.

Connector installation location.

This is where, whenever you want Cognos, whenever you need connectivity to Cognos?

It could, on a desktop, you could put on Tableau server, uh, connector and the Client server kind of form of, which we recommend. Basically, you’re connecting your Tableau Desktop to a connector on a server.

The Connector software doesn’t need to be installed on Cognitive Service. Although, we’ve seen it, too, for POCs where you have.

But it doesn’t have to be on the same server that your Cognos installations are.

Environmental impact on Cognos.

You’re going to generate a little bit of a load and Cognos Servers that’s similar to an interactive report.

So, when people are, for example, in report, the report writing tool, and they’re dragging and dropping peel’s, and then, going, from, page, designed, page preview, or running it, That’s kind of an interactive report.

You’ll see that as, what’s generating the load, OK, going back to what I was saying. In terms of like creating extracts, you definitely don’t want to have your connector, be used to extract the entire data warehouse over to The Tableau, was never meant for that. But, the little direct query is how we’re doing.

You’re going to see that as interactive report user activity on the Cognos environment.

And, of course, the mode2 users, they tend to be more interactive, OK, which does increase your load on the cognitive service because you’re in Tableau. You’re like, I was showing you. I’m creating a graph. I’m dragging a measure.

Each one of those interactions is going to cross a little bit of a load on the Cognos server, but these queries, of course, tend to be summarized right? Or, not bringing up. Brack back the entire journal I detail report. They’re generally or creating a graph, summarized view, things like that, OK?

As part of the development life cycle.

You do want to ascertain the net load the cargo system as you begin rolling this product out.

Licensing requirements from perspective of direct query. So, if I’m logging of I’m a Tableau user and, I’m logging indirectly the Cognos, I use the License and Analytics user or equivalent, right?

If you’re doing extract import.

You do need a Cognos Analytics user license to create it.

Um, but the one thing that is useful for this, you may only need like one analytics user who actually creates the extracts imports.

So by creating extract files or extract hyper files into Tableau Server one guy made me, maybe it has the job of doing that.

But then, you’re tableau users, they could have 10 to 15 users using those extract files on Tableau server.

They don’t need it. They don’t need it. We’re just using one analytics license user to create it.

But, if you, if they’re doing direct query all the time, then that’s a wonderful while you know, they need to have a Cognos license as well, a tablet license.

Um, again, the security automatically enforce security defined within Cognos. We would kind of mentioning that, whatever security is defined in the package, as weather. Also, if we have very complex, row level security in the package, the connector will respect that.

Framework manager modelling requirements. No special modelling requirements are needed.

You know, the framework manager will do the joins between the query subjects between the rod tables of your data warehouse and presented to the presentation layer.

People who access kindness don’t know when you’re in Cognos and there’s joins below the presentation layer. They’re bringing fields from a dimension table to bring a field for the measures. All the joins are happening below the scenes, right? Same thing with Alex Connector, it creates a dummy joins by default, the AAA link. And then, it respects the joins as defined in the FM model.

Method for accessing Cognos? So, again, what we were demonstrating, if you are using the character, he, we’ve seen demos previously, there was, originally, way back.

more of, an ODBC legacy type connection, Custom connectors for SQL Server, Power BI and an ODBC legacy connection for Tableau. Now we are recommending the use of just using the SQL Server connection whenever going from Power BI Tableau to the connector.

Of course with your subscription.

Support and maintenance has provided By Senturus.

This is just really an Architecture slide.

Kind of quickly summarizing what’s happening here in Tableau.

On the right side, you have your sources. You have your Cognos environment. Right? This and tourist piece, the MIRAs is really the tourists connector.

You basically connect to the through the Senturus Analytics Connector. Tableau connects, various interests, connector.

Then, this ensures the Connector is connecting to packages, reports, or data modules to get back to your data when I did the live connection.

And, basically, going through that top piece, right? It’s going through that chain of events is going to the Senturus Connector.

It’s doing a query in the Cognos Analytics environment, threw the package back to your database and then returning the results back to Tableau.

Then, what you could do with Tableau is publish it to your Tableau server and it’s doing the same thing.

So, it’s just really the same thing. It’s very simple.

Power BI architecture is very similar as well.

The top is your Senturus Analytics Connector.

Again, the Senturus Connectors connected to your IBM Cognos environments and the database, and within Power BI, the upper left, Power BI, you can connect to the Connector via a live connection, which is what I showed, or an import.

Then, you could publish your Power BI visualization up to the Power BI Service cloud.

And then the Connector is connected, live, or import connections through the on premises gateway that Power BI supports.

The on-premises gateway then communicates back with Senturus Analytics Connector to get to that same route. So, Power BI, yet, the desktop.

Then you have the publish to the Power BI service, and that’s a little bit of a difference from the way the Tableau Service working.

We have the on-premises gateway from the Power BI, Senturus to connect through.

To save much time and money we’ve stopped creating metadata from scratch for saving hours.

Lot of hours, weeks of time, depending on the number of packages you report complex day.

You’re stopping converting reports outside converting reports out of outside of Cognos, right? You maximize your Cognos investment now.

There’s a lot of maybe move and assist, say, you know, the Cognos, Power BI or Tableau, but maybe Cognos is there because you really have a lot of lot of legacy stuff there. You have to use the bursting feature, for example. And cognitive was a very good tablet as a support it very well, a lot of reasons why you want to keep your Cognos the best. And you want to be able to maximize it, Right?

This is one way to maximize your Cognos investment. And, of course, your business metrics. You want to make sure that a measure you show in Tableau is going to yield the same value as a measure show and Cognos as a measure you show in Power BI.

So, in a sense, coexistence or cut the cord are we doing? Are we going to just cut the cord from Cognos Analytics, and start from scratch into Power BI and Tableau, which is what the thrust of our presentation is here, versus coexisting right? Nice, Kumbayah world with all three.

The bimodal approach, Power BI, Tableau, analytics in terms of like bimodal one, and I will say, I’ll add a pitch to this, too.

I will say that the Cognos Analytics product has evolved quite a bit since the first onslaught of Power BI and Tableau.

Lot of the features you see in those products are now existing in Cognos Analytics and trends, tablet data, modules and datasets, and even better, dashboard. Features of court Tableaus up. There create visualizations. If you’ve got to use it, you use it, but Cognos Analytics does have all the same features.

But something you might want to take a look at.

Thanks for all of that, Pedro. Just some quick wrap up stuff here for today’s webinar, and we do have a few customer case studies on our website for specific uses, analytics connected, and so you can find those. Senturus.com, if you’re interested in getting into a little more detail about specific use cases for the Analytics Connector.

So If you’re interested in trying out the Connector In your environment. We do offer a free 30-day trial that doesn’t support from the Senturus team.

You can request a test drive, also at our website, Senturus.com/product selection, Analytics Connector and we’re happy to set up trial for you.

In addition to that, you can find lots of additional resources on our website.

We’ve been in this business for a couple of decades now, We’ve got a lot of information on our sites, both and past webinars, blog, posts, technical tips, demos of our products. A lot of stuff out there for you. So, there’s a treasure trove of information which is there for the review. May also want to let you know about a few upcoming webinars that we’ve got a pretty full roster here with summer coming out. Early next month, we’re getting acquainted, getting acquainted with a quarter. So, if you’re interested in Incorta’s direct data platform, we recently partnered with Incorta and we’ll be doing the webinar.

We also have a webinar coming up on an introduction to the Azure Data Platform and how to use some of the resources, usually Azure cloud or your needs.

And the beginning of September, we have intro to data visualization using Python.

If you’re interested in getting down into the details of Python, for accessing your data, generating visualizations and join us for them.

Here at Senturus we are focused on BI modernizations and migrations across the entire stack. We have lots of customers and have experience 21 plus years along with the BI and analytics space.

We have a team that’s large enough to meet all of your needs, but also small enough to really give you focused personal attention. And we do have long string history to back that up.

If you’re interested, in joining the Senturus team, we’re currently looking for a Senior and Microsoft BI consultant and a managing consultant.

So, if you’re interested in joining us, please send your resume to [email protected]

You can also find more details with detailed job descriptions on our website, And we are past the top of the hour here. As we get into the Q&A session, the good news is, most of your questions have already been answered, so, I’m just going to call out a couple of items here before we wrap up.

There was an early question about whether there’s a limit to the number of rows in the results, and, I believe the answer is that there is no fixed limit because we pull that data out of Cognos essentially, as CSV under the hood.

Obviously, there’s a performance impact on how much data you’re pulling.

There were some questions about Cognos licensing roles which were answered, but just to re articulate for the group, any user who is using the Connector to pull data out of Cognos, that user needs to have a Cognos license that allows report creation. And, so, in Cognos 11, that’s an analytics user or above in older versions of Cognos?

I think it was called Professional Author and above.

There was a question about what features and functionalities are available in Cognos that can be achieved by using Power BI and Tableau? Pedro touched on this a little bit ago. Today, Cognos does provide dashboarding capabilities. So, there’s more feature parity today than there used to be, but we still find that.

A lot of organizations have users who are really fond of Tableau and Power BI for generating visualizations, so that the compelling reason that customers choose to use the Connector as they, they want to use Power BI and Tableau as their front end. But, they also want to be able to take advantage of the curated data that’s already been through Cognos and the art, and we very significant investment in Cognos.

There are many cars that many organizations already have.

There’s a question of pricing here at the very end that just came in. You should reach out to our sales team to discuss that there are multiple licensing options, depending on the size of your user base, and whether you want to use the Connector. So, our sales folks are happy to answer questions on that.

And, with that, I’m going to go ahead and wrap us up, because I know we’re over time here. We do appreciate you joining us. Thank you again, Pedro, for a great presentation.

And we hope that all of you will join us again for a future than Senturus webinar. And thanks, and have a great day, everybody.

Connect with Senturus

Sign up to be notified about our upcoming events

Back to top