Previous Topic: Managing Repository ObjectsNext Topic: Using Owner Roles with Repositories - Overview


Create a Repository Object

You create a repository object...

Follow these steps:

  1. From the Administration tab, click the Repository subtab.
  2. Click Create.
  3. Complete the following required fields:
  4. Click Create.

    The repository object is created with your basic required settings.

Add Owner Roles to a Repository

You can add owner roles to a repository.

Follow these steps:

  1. From the Administration tab, click the Repository subtab.
  2. Select your repository.

    The edit Repository object panel displays.

  3. On the Definition tab, find the Owner Roles section:

    You view the Available Roles and Selected Roles lists.

  4. Select one of more names in the Available Roles list.

    Hold Ctrl or Shift while clicking to select more than one Role

  5. Click the single right arrow between the two lists to add the selected Role (s)
  6. (Optional) Click the double right arrow to add all the Roles to the Repository.

    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.

  7. Click the Update button near the top right of the panel.

    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.

Understanding Report Access

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: