Page History
...
Table 9-5 Parameter values for Editing a role
Parameter Description
...
| Parameter | Description |
|---|---|
| Action | The action we wish to perform on the defined role. Value: Edit Mandatory: Yes |
| Role- |
...
| name | The name of the role we wish to edit. Mandatory: Yes |
| Role- |
...
| scope | The scope of the rode the user wants to define the permissions on. Values: technology, application, Tier, or instance. Mandatory: Yes |
| Role-new- |
...
| name | The new role name. Mandatory: No |
...
| Permissions | The permissions we wish to assign to this role. Mandatory: No |
...
|
...
|
...
|
...
|
...
|
...
| |
| Resources |
...
The resources the role permissions apply on. |
...
|
...
|
...
Mandatory: Yes, if permissions are changed. | ||
| Nodes |
...
This parameter is relevant only to ‘technology’ role scope. Use this parameter to define technologies permissions on specific nodes. If this parameter is not defined the technology permissions will apply on all nodes. Node-name: the name of the node Nodes that are already assigned to the role and are not specified in edit will be removed from the role definition. If no proxies are specified in edit mode then the role’s proxies will remain unchanged. Mandatory: No |
Example
In this example we will be editing the following role:• Role
- Role name: test-role1
...
- Role scope: technology
...
- Role permissions
...
- MONITOR.FULL_CONTROL
...
- TUNE.EXECUTE
...
- ADMINISTRATE.EXECUTE
...
- Role resources:
...
- Oracle technology
...
- Oracle Applications technology
...
- Role nodes
...
- node1
...
- node2
We will remove the first two permissions and add a new permission – MONITOR.EXECUTE. We will set the role to apply on all nodes and also change the role name to ‘test-role1-updated’. After the edit operation is completed, the role definition will be:
...