Policy Properties

Applies To: Opalis 6.3

Opalis Integration Server enables you to configure properties for individual Policies.

To define the properties of a Policy

  1. Right-click the Policy tab and click Properties. The Policy Properties dialog appears.

  2. To configure the settings on the General tab:

    1. Type the Name of the Policy.

    2. Type a detailed Description of the Policy.

    3. Click the ellipsis (...) button to browse for a Schedule to assign to the Policy. The Policy will only run on the dates and times specified on the schedule. For more information, see Schedules.

  3. To configure the settings on the Action Servers tab:

    This tab displays the list of Action Servers that are assigned to run this Policy. If the list is blank, the default primary Action Server will run the Policy. For more information, see See Action Server Failover and Assigning Specific Action Servers to Run Policies.

  4. To configure the settings on the Logging tab:

    You can select to Store Object-specific and Store Common Published Data items to the Policy log and the Data store, or exclude them. For more information, see Configuring Policy Log Options.

  5. To configure the settings on the ROI tab:

    1. To assign money and time saved when running this Policy, as compared to running the Policy without Opalis Integration Server software, in the Savings section, type the money amount in the Value field, and the time amount in the Time field.

    2. To assign money and time that this Policy costs to run, in the Cost section, type the money amount in the Value field, and the time amount in the Time field.

    For information about using the ROI information, see <Executive dashboard>.

  6. To configure settings on the Event Notifications tab:

    1. If you want to be notified when this policy runs for more than a specified number of seconds, enter a value in the seconds field.

    2. Select the check box if you want to be notified when the Policy fails to run.

  7. To configure settings on the Run Behavior tab:

    You can specify how a policy will run when it is executed by the Action Server. Parallel Execution enables you to execute multiple requests for the same Policy at the same time.

    To configure the maximum number of simultaneous requests for a Policy, type a value in the Maximum number of simultaneous requests field. The following limitations apply:

    • You cannot execute multiple, simultaneous requests for Policies that start with Monitor objects. If you try to change the maximum number of simultaneous requests for these Policies, the Policy Properties dialog resets the number to 1 and displays an error message.

    • Opalis Integration Server will execute simultaneous requests for Policies up to the maximum Policy processing limit set by the Action Server Policy Throttling utility. For more information, see the “Policy Throttling” chapter of the Administrator Guide.

    • You cannot execute multiple, simultaneous requests for Policies that contain Modify Counter objects because simultaneous executions of the same Policy that modify (set, reset, increment, or decrement) a Counter can cause the Counter value to become unreliable. You can, however, read the value of Counters in Policies that execute simultaneously.

    • Do not run simultaneous requests for Policies that interact with third-party products, such as ticketing or system monitoring tools, unless you have a thorough understanding of how these tools handle parallel processing. If the third-party application cannot handle parallel processing, or if you do not know, leave the maximum number of simultaneous requests at a value of 1 for these Policies.

    • Plan your changes carefully. Before you change the maximum number of simultaneous Policy requests, consider the tasks performed by the Policy, and verify that each Policy instance will be able to complete successfully. For example, file and folder operations can be sensitive when multiple, simultaneous instances of the Policy are running. If your Policy creates a folder, places files into it, and then deletes the folder when it is finished, one instance of the Policy may delete the folder before other instances are finished with it. In this case, you should leave the maximum number of simultaneous requests for these Policies at a value of 1 to avoid these conflicts.

    If applicable, select the Policy Mode that you want to use to run this policy, either Pipeline mode or Legacy mode. These two modes run very differently and we recommend testing your policy thoroughly if you have switched the mode of the policy.

  8. To configure settings on the Policy Data tab:

    When creating Nested Policies, you may want to set output data of a child policy. The Policy Data tab allows you to create the schema for the data that will be published by this policy when it is run by the Trigger Policy object. Use Add, Edit, and Remove to create each named Policy Data that will be published. Use the Publish Policy Data object to set values for the Policy Data when the policy is executed. The Policy Data is used when the Trigger Policy is used to trigger a policy and the Wait for completion setting is enabled.

  9. Click Finish to save your settings.