The benefit is that the administrators do not need to manage a password or maintain the account. The network service Cognos Service account under which IBM runs must have access to all required resources, like printers, and have the rights to log on as a service and act as part of the operating system. The network service account must also be a member of the local administrator group.
For example, to print reports using a network printer, the account must have access to the network printer, or you must assign a logon account to the IBM Cognos service. The few times an administration action was required, the Cognos administrator signed in using the Cognos network service account, made changes, and then logged back out.
The client preferred that the Cognos administrator use the Cognos Services Account only for admin specific actions and not as their primary account. They were paying for a Cognos Analytic user license for the Cognos administrator and they were also paying for a Cognos Administrator license for the Cognos Services Account.
So, if the Cognos administrator is the one who sets the network service account up and responsible for maintaining it, then all they need is a Cognos Administrator license for the administrator. Under the IBM Passport Advantage Agreement an authorized user means that each person must have their own license, no sharing and it is not a concurrent license. If the administrator of the Cognos BI system has a Cognos Analytics administrator license, there is no additional licensing required for the Cognos Services Account.
It is common for admins to have multiple logins for Cognos, their everyday login, and the network service account. However, if you have other users who do not have administrator licenses, and you ask them to login with the network service account you would most likely be violating the IBM licensing and could fail an IBM licensing audit because the user was accessing admin functionality they did not own.
If the client has the Cognos network Service account set up and they have 3 different administrators that need to log into that account periodically, and all of them have Cognos Analytics Administrator licenses then they still would not need to have a separate license for the Cognos Network service account. Basically, if everyone that logs into the network service account has their own IBM Cognos Administrator license, you are good. We can view those members also, but there could be accounts which are members of both groups which should not be double counted.
The two external groups are then added as members to the Cognos role. Now the accounts are two levels removed from the capability making them even more difficult to count.
With some effort it is possible to navigate through all the hierarchies of groups, roles and accounts and manually build a list of account capability access. One of these is the expandMembers function which will recursively expand group and role memberships returning a list of accounts. But none of these are easy or automated and can get progressively more difficult with growth and changes over time.
Photo by Serge Melki. Topics: Cognos BI administration. Request a Demo Support info envisn. Granting Permissions with Groups and Roles While it is possible to grant individual users accounts access to capabilities, groups and roles are generally used for this purpose as it makes the management easier.
Posts by Popularity. Under Permissions , click Add. Navigate to the appropriate groups or users and move them over to the selected entries and click OK. In the Permissions window, click the groups or users and select Deny for execute and traverse.
By taking the time to follow these steps and set up your system from the outset, you are making future maintenance easier. This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings. If you disable this cookie, we will not be able to save your preferences.
This means that every time you visit this website you will need to enable or disable cookies again. New roles and associated capabilities: For details on use restrictions, refer to the IBM website for license information.
Setting up Cognos configuration The first step to enabling these entitlements is setting up Cognos Configuration. Creating the analytics administrator role With configuration taken care of, you can move on to creating the Analytics Administrator role in Cognos Analytics portal. Cleaning out everyone The above steps of removing Everyone need to be done in multiple locations.
Everyone needs to be removed from the membership of the following: Adaptive analytics users Authors Consumers Data manager authors Mobile users Metric users PowerPlay users Readers Analysis users Cognos Insight users Controller users Express authors Metrics authors Planning contributor users Query users Adding the user roles Your Analytics Explorer and Analytics User roles need to be a member of a number of roles as per the matrix above. Repeat these steps to add groups or users in the Analytics Explorer or Analytics User licensed role to the following: Consumers Metric Authors Analytics Explorer only Mobile Users Modelers The information distribution role The final role you need to address is the Information Distribution role.
Repeat the steps for the capabilities of: Web-based modeling Upload files Dashboard Conclusion By taking the time to follow these steps and set up your system from the outset, you are making future maintenance easier.
Connect with Senturus Sign up to be notified about our upcoming events Your email Subscribe. Privacy Overview This website uses cookies so that we can provide you with the best user experience possible.
0コメント