What would the provisioning be for someone who needs to create business rules for one individual BSO cube in Version 220.127.116.11? Business Rules will be developed via the Calculation Manger directly in the appropriate BSO application. In our test environment, I would like to limit them to this BSO cube as well as limit their functionality to create, validate, deploy and launch new business rules against this cube? Any ideas?
Yes, I have read several documents and thanks for sending this. From what I read if I assign Calc Manager Administrator that would allow our end user to much access? I don't want them to be able to modify, delete our existing business rules that aren't associated with this BSO cube or even the ones associated with our 17 planning applications. (this BSO cube has no planning component) I also thought the Essbase Adminstrator role would also allow too much access since this end user would now be able to see and edit all the other cubes in EAS. This end user should not be able to see or edit our other planning/essbase cubes.
Thanks for sending and I have read this document as well when we were on Version 9; we are now on Version 11 but have read the security guide. Background to this issue: I provisioned a group to the new BSO cube as Datasbase manager as well as provisioned for Reporting and Analysis as Viewer and Explorer. With our test ID, we can access the Calc Manager application and create business rules and save them but at some point our Essbase server crashes. I am not sure what is going on or why our essbase crashes. Not even sure if it is related to the provisioning (it just seems to crash while using this Test ID). We have several planning, BSO and ASO cubes and need to limit this user to their cube and their business rules. They should not be able to edit or view our other applications and our other business rules. So the Calc Manager Administrator and Essbase Administrator gives them too much access in our environment?