Hi,
In this Page we are going to see How we used to Provision the Users to the Hyperion App's
First Is that a better choice to create a Group and Assign the access to the Group or Provisioning the Access to the user is a better choice?
Lets see which is better ?
If the Client requested us to create a single user and provisioning the Access to the Hyperion App We can go with provisioning a user without creating a Group but...
If the client requested us to create a 100 users and Provisioning to multiple Hyperion App's its better to go with creating a Group w.r.t to the App Name eg...HFM_Admin/ HFM_Read/EssAdmin...Provisioning that Group and Assign the respective users under Group.
Slight difference in Provisioning the Users among the Hyperion App's
For Essbase:
Create a user in HSS & Provision After That refresh the filters in Essbase using EAS and Refresh the Security filters in Planning using workspace
For Planning:
Create a user in HSS & Provision w.r.t to the dimensions like Entity/product/Scenario/Custom ...
After that Refresh the Security filters in the Workspace
For HFM
Create a user in HSS & Provision w.r.t the Read only access or Admin Access.We have an excellent feature in HFM that we can restrict the user w.r.t the location or Scenario using Security Class dimension....
For FDM
Create a user in HSS and Provision to FDM App.We have to do an additional activity to get the access to FDM Application i.e...Login into the FDM App using weblogon and select UserManagement under Administration and select the user which we provisioned w.r.t all locations as an Admin /Intermediatter....
HSS Url : http://servername:28080/interop/index,jsp
We can access the shared services console in workspace aswell
Workspace Url : http://servername:19000/workspace/index.jsp
Steps to Create a user:
a.Login to the HSS and expand Native Directory
We have access to only Native directory not to Active directory called MSAD/LDAP
b.Create a Group/User by click right on the respective member
c.Click right on the Group/User once we created and say Provision
d.Assign the Respective Roles as per the Client Requirement and save it .
Please read this Page and let me know if you have any questions....
In this Page we are going to see How we used to Provision the Users to the Hyperion App's
First Is that a better choice to create a Group and Assign the access to the Group or Provisioning the Access to the user is a better choice?
Lets see which is better ?
If the Client requested us to create a single user and provisioning the Access to the Hyperion App We can go with provisioning a user without creating a Group but...
If the client requested us to create a 100 users and Provisioning to multiple Hyperion App's its better to go with creating a Group w.r.t to the App Name eg...HFM_Admin/ HFM_Read/EssAdmin...Provisioning that Group and Assign the respective users under Group.
Slight difference in Provisioning the Users among the Hyperion App's
For Essbase:
Create a user in HSS & Provision After That refresh the filters in Essbase using EAS and Refresh the Security filters in Planning using workspace
For Planning:
Create a user in HSS & Provision w.r.t to the dimensions like Entity/product/Scenario/Custom ...
After that Refresh the Security filters in the Workspace
For HFM
Create a user in HSS & Provision w.r.t the Read only access or Admin Access.We have an excellent feature in HFM that we can restrict the user w.r.t the location or Scenario using Security Class dimension....
For FDM
Create a user in HSS and Provision to FDM App.We have to do an additional activity to get the access to FDM Application i.e...Login into the FDM App using weblogon and select UserManagement under Administration and select the user which we provisioned w.r.t all locations as an Admin /Intermediatter....
HSS Url : http://servername:28080/interop/index,jsp
We can access the shared services console in workspace aswell
Workspace Url : http://servername:19000/workspace/index.jsp
Steps to Create a user:
a.Login to the HSS and expand Native Directory
We have access to only Native directory not to Active directory called MSAD/LDAP
b.Create a Group/User by click right on the respective member
c.Click right on the Group/User once we created and say Provision
d.Assign the Respective Roles as per the Client Requirement and save it .
Please read this Page and let me know if you have any questions....
No comments:
Post a Comment