You create a repository object...
Follow these steps:
For example, you enter West Coast CA View to provide geographical and product information about this repository.
The available Repository Locations list will show only repositories of the type you select. For example, if you select CA View, no CA Dispatch or CA Bundl repositories will be listed as possible repository locations.
The location address consists of a mainframe system ID, a DRAS system, and either a CA View, CA Dispatch or CA Bundl system.
For example:
ENFSYSID:DRASA:SALESVW or ENFSYSID:DRASB:SALESBDL
You can refresh the list of choices with the DRAS Discovery button.
For example, you assign System Admin and East Coast Group Admin.
The repository object is created with your basic required settings.
You can add owner roles to a repository.
Follow these steps:
The edit Repository object panel displays.
You view the Available Roles and Selected Roles lists.
Hold Ctrl or Shift while clicking to select more than one Role
All of the Roles in the Selected Role list can now have the possibility of accessing this Repository. See the explanation above for other limitations on Repository access.
The Roles are added.
Roles can also be given access to a repository at the Roles panel. However, the System Administrator role cannot be edited from the Role panel. To add the Systems Administrator role to a repository, it must be added from this panel.
Just because a role has access to a repository, does not necessarily mean that every user in that role can view every report in that repository. Limiting the access of a role to repositories is one of several ways of limiting access to reports in CA OM Web Viewer and the base repository systems.
Limiting Report Access through Mainframe Repository Security
In order for a user to see report information, their mainframe account, or proxy profile must have access to the report in the base CA View, CA Dispatch, or CA Bundl system.
Report access can be further limited within the security setup in the mainframe repositories. Be aware that CA OM Web Viewer users cannot access reports that they are not, or their Profile is not allowed to access through the mainframe system.
For more information on controlling user access within the base CA View, CA Dispatch, or CA Bundl systems, see the product documentation for those products.
Note: As a work-around, set up a profile account that has access to a report in which the user would not normally have access.
Limiting Report Access Thorough the Use of Subscriptions
Report access can be further limited with subscriptions in CA OM Web Viewer. Basic User roles only let their users access reports assigned to the role with the subscriptions.
Notes:
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|