# WLOC Administration Console Online Help

# Define constraints using named constraints (Smart Pack)

Before you begin

Review Define and assign policies.

WLOC provides preconfigured Smart Packs that define a set of named constraints that you can use to place requirements on some common measurements of service health and performance.

Note: Smart Pack definitions intended for use with Coherence 3.4 are bundled in the `coherence-wloc.jar` file. See Setting Up a Coherence Management Gateway.

To define a constraint using a named constraint:

1. Access the Constraints page in one of the following ways:
   - Click the Policies tab in the WLOC navigation bar, click the Definitions tab, and click the Rules tab.
   - Click the Home tab in the WLOC navigation bar and click Rule Definitions under Manage Policies.

   The list of currently defined constraints is displayed in the Rules table.

2. Click the Smart Packs tab to view a list of the predefined of named constraints.
3. Click Add Policy Definition.
4. Set the fields for the constraint, as required:

   Field | Description
   --- | ---
   Name | Name of the constraint.
   Type | Select Based on a named attribute.

5. Click Next.
6. Set the additional fields for the constraint.

   Field | Description
   --- | ---
   Name | Name of the constraint. (You can edit the name that was specified on the previous page.)
   Priority | Priority of this constraint over other constraints. The higher the number, the higher the priority.
   Attribute | Name of the attribute. Select an attribute from the drop-down list. The list includes all of the attributes that are delivered with the pre-configured Smart Pack. Select one of the named constraints to define an upper or lower threshold for the following values: Free heap size for a JVM (MaxFreeHeapSize, MinFreeHeapSize) Average heap size for a JVM (MaxAverageHeapSize, MinAverageHeapSize) Free physical memory (MaxFreePhysicalMemory, MinFreePhysicalMemory) Average free physical memory (MaxAverageFreePhysicalMemory, MinAverageFreePhysicalMemory) Used physical memory (MaxUsedPhysicalMemory, MinUsedPhysicalMemory) Average used physical memory (MaxAverageUsedPhysicalMemory, MinAverageUsedPhysicalMemory) JVM processor load (MaxJVMProcessorLoad, MinJVMProcessorLoad) Average JVM processor load (MaxAverageJVMProcessorLoad, MinAverageJVMProcessorLoad)
   Value | Value of the attribute that triggers the event.
   Evaluation Period | Interval of time (in milliseconds) to wait before re-evaluating the constraint.
   Service State | State in which the service should be in order for the constraint to apply. Valid options include: deployed and undeployed.

7. Click Finish.

   The constraint is added and the following confirmation message is displayed:

       New policy created successfully

After you finish

- Modify constraints.
- Create actions and set up action pipelines to run when policy rules are violated, as described in Define actions and Define action pipelines.