Permissions depend on who owns the components being managed or who is responsible for particular management functions. You can assign permissions by functional group (such as administrators, operators, or a data warehouse team) or by ownership. You can then add or remove individual users in a group.
For example, a data warehouse team would monitor the extraction, transformation, and loading (ETL) processes to populate a data warehouse. Create a DW group containing the data warehouse team members. Then, give this group List and Open permissions to a process watch object providing all shortcuts related to the ETL processes.
Administrators are assigned greater permissions than general users. A database administrator can have control over processes to update a data warehouse or to restore or back up certain databases. If you are developing for a complicated enterprise environment with many different roles and ownership, consider this approach. Map out ownership in a spreadsheet or other format for the groups, users, and roles to assign appropriate permissions.
Ownership for a process (or any automation object) is initially assigned to the user under which it is created. Ownership can be changed.
Defining permissions for actions users can take at runtime is handled by the permissions editor in CA EEM. Members of the default PAMAdmins group have full permissions on all folders and all automation objects. Members of the default PAMUsers group have no permissions on any folder or automation object. Content designers are typically members of the Designers group.
A content administrator or the owner of a folder can assign you permissions on the folder with the Set Owner property. Folder permissions are inherited by automation objects added to the folder. An administrator with CA EEM credentials can assign you permissions on automation objects and folders in CA EEM.
Note: See the Content Administrator Guide for details.
|
Copyright © 2014 CA.
All rights reserved.
|
|