Information Analyzer Roles

This forum contains ProfileStage posts and now focuses at newer versions Infosphere Information Analyzer.

Moderators: chulett, rschirm

Post Reply
metadatamen
Premium Member
Premium Member
Posts: 42
Joined: Wed Oct 26, 2016 8:38 am

Information Analyzer Roles

Post by metadatamen »

Let's assume that we have a multi engine & IADB topology, and they are configured for different IA project as below.

IA Project 1 - Points to IADB 1 and Engine 1
IA Project 2 - Points to IADB 2 and Engine 2
etc.

And we gave CM Import & IA Data Admin Access to users on these 2 projects so they could import their Metadata through IMAM and IA. And other access that are needed to build IA rules, just that they don't have IA Project Admin Access since this would let them delete any IA project.

Now the issue is, they couldn't see their IA project properties, and because of that they couldn't import the metadata into their project. The funny part is they imported the metadata by themselves through IA and IMAM, but they can't add them in their project.

Users have been depending on Admin to do this.

Have anyone come across this issue? Do we have any way of handling this better? I don't want to have Project Admin access, but they should be able to add their metadata to their project.
metadatamen
Premium Member
Premium Member
Posts: 42
Joined: Wed Oct 26, 2016 8:38 am

Re: Information Analyzer Roles

Post by metadatamen »

Question 2 on same context:

We have been using DQEC and Stewardship Center extensively with same architecture as mentioned above.

We gave access [not admin] for User 1 on IA Project1 so he can import metadata and build rules.
And he should be able to login to DQEC to manage the exceptions by himself to push them to Stewardship center.

When this same User 1 log in to DQEC, he is able to see all IA Project rules [but we gave access on IA only for Project1] and it's exceptions irrespective of any DQEC roles that we give except [Exception Management Business Steward]
But "Exception Management Business Steward" doesn't have manage exception access.
Again they have been depending on Admin to do this activity.
Do we have a solution for this?

Or do we have a back end command or Rest API function to manage the exceptions in DQEC, mainly to push the exceptions to Stewardship center. How other customers are solving this problem or what IBM would propose for this?
Post Reply