| |
Roles and Policies: Roles
Buttons Column Display Related Tasks Related Topics
Use this table to view, add, modify or remove global or scoped security roles for this security realm. Global roles are listed in the Name column under the Global Roles node. Scoped roles are listed in the Name column under the individual resources that they secure.
- Notes:
- This table does not list scoped roles for JNDI resources or Work Context resources. To see these scoped roles, view the Security tab for each JNDI node or Work Context object.
- If you imported security roles for EJBs or Web applications from deployment descriptors using the Install Application Assistant, you must activate changes to access the roles.
Column Display
Name Description Name Organizes all of the domain's roles in a hierarchical tree control. Global roles are listed under the Global Roles node. Scoped roles are listed under the individual resources that they secure.
For example, all EARs that have been deployed are listed under the Deployments node. The MedRecEAR node contains a Roles sub-node that lists roles that are scoped to the entire application and all of its modules. The MedRecEAR node also contains one sub-node for each module within the EAR.
Each module within the EAR also contains a Roles sub-node. This Roles sub-node lists roles that are scoped to the entire module.
To Access Scoped Roles for This Resource Type... In the Name Column, Click "Roles" Under... Administrative Domain > domain_name
For example: Domain > mydomain > RolesEnterprise application (EAR) Deployments > EAR_name
For example: Deployments > MyEAR > RolesEnterprise Information System (EIS) Deployments > RAR_name
For example: Deployments > MyRAR > RolesEJBs and Message-driven Beans (MDBs) (within an application) Deployments > EAR_name > Modules > EJB_name
For example: Deployments > MyEAR > Modules > MyEJB > RolesEJBs and Message-driven Beans (MDBs) (stand-alone) Deployments > EJB_name
For example: Deployments > MyEJB > RolesJCOM JCOM > JCOM_class_name
For example: JCOM > myJCOMClass > RolesJDBC data source modules (within an application) Deployments > EAR_name > Modules > Data_source_name
For example: Deployments > MyEAR > Modules > myJDBC > RolesJDBC data sources (system resources) JDBC > JDBC_resource_name
For example: Domain > myGlobalDataSource > RolesJMS modules (within an application) Deployments > EAR_name > Modules > JMS_module_name
For example: Deployments > MyEAR > Modules > MyJMS > RolesJMS modules (system resources) JMS > JMS_resource_name
For example: Domain > myJMSResource > RolesJNDI resources Not listed in this table. Instead, view the Security tab for each JNDI node. Server Server > server_name
For example: Domain > myserver > RolesWeb applications (within an application) Deployments > EAR_name > Modules > Web_app_name
For example: Deployments > MyEAR > Modules > MyWebApp > URL Patterns and RolesWeb applications (stand-alone) Deployments > JWeb_app_name
For example: Domain > MyWebApp > URL Patterns and RolesWeb services Deployments > EAR_name > Modules > Web_service_name or
Deployments > Web_service_name
depending on how you deployed the Web service. For example: Deployments > MyEAR > Modules > MyWebService > RolesWork Context objects Not listed in this table. Instead, view the Security tab for each Work Context object. Resource Type Indicates the type of WebLogic resource that represents the module that is listed in the Name column.
Role Policy If you have defined conditions for the role that is specified in the Name column, this column displays a hyperlink that enables you to view or modify the conditions.
Buttons
Name Description Edit Role Enables you to create conditions for the role that is specified in the Name column. The button is enabled when both of the following are true:
- You have not defined conditions for a role that is displayed in the Name column.
- You select the radio button next to a role for which you have not defined conditions.
|
