Page History
...
Table 9-3 Role scope parameters
| Role scope |
|---|
...
| parameter | Resource information | Example |
|---|---|---|
| technology | technology |
...
| -code: the technology code the permission should be granted |
...
| on | <parameter technology-code="OR"/> |
| environment |
...
| environment-name: the name of the application the permission should be granted |
...
| on. | <parameter environment-name="Default"/>
|
...
| |
| apptier |
...
apptier-name: the name of the Tier the permission should be granted on |
...
environment-name: the name of the application the Tier belongs |
...
to. | <parameter apptier-name="Oracle" |
...
environment-name="Default"/> |
...
| instance | instance-name: the name of the instance the permission should be granted on. technology-code: this parameter is optional, specifies the instance technology code. This parameter should be used if the instance name is not unique. server-name: this parameter is optional, specifies the server the instance is installed on. If this parameter is specified the technology code parameter must be specified as well. This parameter should be used if the instance name and technology are not unique. |
...
<parameter instance-name="ORCL" |
...
technology-code="OR" |
...
server-name="orcl-server"/> |
Example
In this example we will be adding two roles as follows:• First
- First role definition:
...
- role name: test-role1
...
- role scope: technology
...
- role permissions:
- role permissions:
...
- MONITOR.FULL_CONTROL
...
- ADMINISTRATE.EXECUTE
...
- role resources
- role resources
...
- Oracle technology
...
- Oracle Applications technology
...
- role nodes
- role nodes
...
- node1
...
- node2
...
- Second role definition
...
- role name: test-role2
...
- role scope: application
...
- role permissions:
- role permissions:
...
- MONITOR.VIEW
...
- role resources:
- role resources:
...
- All applications
The roles parameters file will look as follows:
...