Create application policies

In the Resource Policies portlet, the main Composite Application policy defines the limits for application size, frequency of use, and periods of no modification. You can keep the default policy settings for the main Composite Application policy or modify them. Then you can refine the main policy by creating child policies to assign to the different classes of applications that you need to monitor.

When you create child policies for composite applications, you create policy rules and conditions or reuse existing rules and conditions that are available in the Personalization Navigator and Personalization Editor. For detailed information about working with policies, see the Help topics that are available from the Resource Policies portlet.

Here is a preview of viewing and refining the Composite Application policy:

1. From the product banner, click Administration -> Access -> Resource Policies.

2. To view and edit the main policy settings for composite applications, display the policy menu of the portal resource Composite Application and click Edit Policy.

   • The policy specifies and monitors the limits for application size, frequency of use, and periods of no modification.

   • The policy also sets the warning thresholds for application size, inactivity, and staleness and who should receive email notices of application status.

   • Notices include warnings for applications with conditions approaching policy limits and messages citing violations of applications that have exceeded the limits set by the policy.

     You can select one or both of the following notification options when you edit application policies:

     • Send email to administrators.

     • Send email to application owner.

     Be aware that application users who are not portal administrators might receive application status notices that refer to them as administrators. This situation can arise if you create a new application role that is based on the default Users role and then specify the additional permissions defined for the default Administrators role: edit the application and control membership. If you do this, you have, in effect, created another administrator role for members of the application. Remember to type a description that indicates that the new role has the additional permissions provided by the default Administrator role: For example, consider reusing the default description, Can edit the application and control membership.

3. The policy also specifies the settings that can be modified in child policies created from this main policy. Policy settings that you can modify in child policies will allow for greater refinement when you specialize the policy for particular subsets of applications, as shown in the example.

4. To perform other actions on the main policy for composite applications, display the policy menu of the portal resource Composite Application and click one of the following actions:

   • Import Policy Definition

   • Export Policy Definition

   • Assign User Access to Policy

5. To specialize the main policy for composite applications, you create child policies. Child policies help you manage subsets of applications. Click the Composite Application policy link to display the portlet view where you can create a new policy based on an existing policy rule or a new rule that you create.
   The new policy will be a child policy of the main Composite Application policy.

6. Before you can create a child policy, create or select a policy rule that expresses the conditions that you need for the new policy. From the policy rule menu, click Create New Rule or Select Rule to display the Personalization Editor.
   Each rule contains one or more conditions. The following attributes express conditions in policy rules for Composite Applications:

   • Category

   • Policy Selection Attribute

   • Template

   You can see how the Template and Category attributes might be used in a rule that expresses the default conditions for composite applications:

   Default Application is
   Composite Application when
   current CompositeApplication.Template is Portal Blank Template and
   current CompositeApplication.Category is Composite Applications

   As shown in the example, the rule for creating child policies used to manage personal, departmental, and division applications might have one or more conditional expressions, each of which is evaluated using the value of the Policy Selection Attribute that you specify as an application parameter in the application template. Refer to the example to see how the Organizational Level rule would appear in the Personalization Editor.

7. After you create application templates, you specify the value of the Policy Selection Attribute by editing the value of this application parameter.
   If new application templates are based on Portal Blank Template, the default value of the Policy Selection Attribute is CompositeApp. This value assigns the main Composite Application policy to any applications that are created from Portal Blank Template.

   1. Consider creating application templates for each subset of applications that you want to manage with child policies. For example, you might create three templates: Personal Application, Department Application, and Division Application.

   2. In the Application Template Library, select a template and click Edit Template Parameters.

   3. Edit the Policy Selection Attribute parameter to add the value that you need for the selected template. Using the example, type one of the following values:

      • Personal

      • Department

      • Division

   4. Edit the parameters of the other two templates, specifying the appropriate value for the Policy Selection Attribute of the selected template.

8. In the applications catalog, when users create new applications, Set Component Properties displays the value of the Policy Selection Attribute as an application parameter. Users can type another value for the Policy Selection Attribute if they want and thereby change the policy assigned to the application.

9. The child policies are displayed in the Resource Policies portlet under the parent policy. Edit the settings of each child policies: From the policy menu of a child policy, click Edit Policy and specify the values you want for each setting. Refer to the example to see how application size limits and warning thresholds might be set in the three hypothetical child policies.

10. After you create child policies and edit their settings, the policies are applied to the appropriate applications by virtue of the Policy Selection Attribute that is defined in the application template. The policy assigned to each application monitors the conditions specified in the policy settings and detects application status, as described in the next section.

Parent

Work with policies for composite applications

Previous

Prerequisites

Next topic

Manage application status with policies

 

+

Search Tips   |   Advanced Search