Before you begin
For URL patterns and EJBs this task is not valid if you are using the DDOnly security model. With this model, the resource ignores policies that you create in the Administration Console. See Manage security for Web applications and EJBs.
You can create a security policy that applies to a specific resource instance. If the instance contains other resources, the policy will apply to the included resource as well.
The policy of a narrower scope overrides policy of a broader scope. For example, if you create a security policy for an EAR and a policy for an EJB that is in the EAR, the EJB will be protected by its own policy and will ignore the policy for the EAR. For more information, see Manage security policies.
To create a security policy for a specific instance of a WebLogic resource:
Each resource instance provides its own Edit Policies page, and you can access it through any of several navigational paths.
The Roles and Policies: Policies page organizes all of the domain's resources and corresponding policies in a hierarchical tree control.
For information on finding resources in the Names column, see Column Display.
The Administration Console displays the resource's Edit Policies page.
BEA recommends that you use the Role condition where possible. Basing conditions on security roles enables you to create one security policy that takes into account multiple users or groups, and is a more efficient method of management.
For more information, see Security Policy Conditions.
The policy appears on the Roles and Policies: Policies page in the Policies table.