Work with policies for composite applications
Use Resource Policies to create and manage policies for composite applications. Policies provide an efficient way for administrators and application managers to monitor and manage application lifecycle.
From the product banner, click Administration > Access > Resource Policies to create and manage policies for composite applications. Starting with the main policy for composite applications, you can create child policies for subsets of applications. When assigned to particular applications, these specialized policies monitor application size and activity according to the policy settings that you specify. Policies are assigned to applications by the value of the Policy Selection Attribute. The value of the Policy Selection Attribute is the name of the condition evaluated and applied by the policy rule for the application. The Policy Selection Attribute is an application parameter. Therefore, its value is set and stored in the application template and is available for editing as an application component in particular applications. You receive notification when conditions in applications reach warning or violation status. From the applications catalog, you can view general or detailed status for each application. Depending on current conditions of an application, you can decide to assign a different policy, edit the policy settings, or perform a maintenance action on the application: backup, archive, restore, or delete.
Review the task previews and the example for creating policies for composite applications and managing application status. When you perform these tasks using the portlets for Resource Policies, Personalization, and Applications, remember to refer to the Help topics and complementary sections of this information center.
If the settings Inactivity violation action or No-modify violation action are set to a value of Archive the application, this has implications on mashup spaces. For details refer to the topic about Mashup spaces.
- Prerequisites
You can create policies before creating applications or vice versa; the sequence does not matter. Before you start, make certain that you understand basic concepts and that you have identified the application requirements of your work site. An analysis of the data elements that create effective business rules for managing applications is essential.
- Creating 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 monitor.
- Manage application status with policies
The status of applications as detected by their assigned policies is initially displayed in the applications catalog. Details about the application, its status, and the currently assigned policy are displayed in the Policy Status portlet.
- Example of an application policy hierarchy
Here is a simple example that illustrates how you might refine the main policy for composite applications with child policies. The example is partial; it does not refer to all of the policy settings for composite applications and it does not illustrate lower-level child policies. This refinement of the main policy is based on applications deployed at different organizational levels within your enterprise and focuses on application size.
- Composite Application policy definition
The definition of the main policy for the portal resource Composite Application is specified in createCompositeAppRootNode.xml.
Parent topic:
Assembling composite applications
Related concepts
Manage portal resources with policies
Related reference
Mashup spaces