Manage Encapsulated Assertions
The Manage Encapsulated Assertion task is used to create, modify, and delete encapsulated assertions. These assertions are then available from the assertion palette configured in the encapsulated assertion properties.
Manage Encapsulated Assertiontask is used to create, modify, and delete encapsulated assertions. These assertions are then available from the assertion palette configured in the encapsulated assertion properties.
To learn more about encapsulated assertions, see Encapsulated Assertions.
(1) One or more policy fragments must be defined before you can create an encapsulated assertion. (2) Avoid modifying encapsulated assertions being used in a read-only policy, as the changes will not be reflected in the policy. For more information about read-only policies, see "Read-Only Entities" in Manage Solution Kits.
To manage encapsulated assertions:
- In the Policy Manager, select [Tasks]> Extensions and Add-Ons > Manage Encapsulated Assertionfrom the Main Menu (on the browser client, from the Manage menu). The Manage Encapsulated Assertion Configurations dialog appears.(1) This dialog box is used solely for the creation and maintenance of the encapsulated assertions. How to add, remove, and use them in a policy is the same as the factory created assertions. (2) To quickly locate an entry, type a few characters of the encapsulated assertion name in the filter box at the bottom of the dialog.
- The following table describes each column (these are set in the encapsulated assertion's properties):ColumnDescriptionNameThe name of the encapsulated assertion as it appears in the assertions palette.Palette FolderThe palette in which this assertion appears.Policy NameThe name of the underlying policy fragment for the encapsulated assertion.InHow many input variables are defined for the encapsulated assertion.OutHow many output variables are defined for the encapsulated assertion.
- Select a task to perform:To...Do this...Create a new encapsulated assertion
You can also create a new encapsulated assertion by right-clicking the policy fragment in the Services and Policies list and then selectingCreate Encapsulated Assertion. If the fragment is already associated with an encapsulated assertion, selectEncapsulated Assertion Propertiesto view the settings.Clone an existing encapsulated assertion
- Click [Create].
- Complete the Encapsulated Assertion Configuration Properties.
Remove an encapsulated assertion
- Select the assertion to clone.
- Click [Clone]. A new encapsulated assertion is created, populated with information from the clone source. The name of this assertion defaults to "Copy of <assertion name>".
- Edit the Encapsulated Assertion Configuration Properties as required.
Ensure that the encapsulated assertion is not in use in any policy prior to removal. If it is in use, removing the assertion will make the policy invalid.View or edit the properties of an encapsulated assertion
- Select the assertion to remove. Use [Ctrl]-click to select multiple assertions to remove.
- Click [Remove].
- Select the confirmation check box, and then click [OK].
Export an encapsulated assertion
- Select the assertion to view.
- Click [Properties]. See Encapsulated Assertion Configuration Properties.
Import an encapsulated assertion
- Select the assertion to export.
- Click [Export].
- Enter a name for the exported file and choose a target directory, then click [Save]. Both the encapsulated assertion and its underlying policy fragment are saved to an XML file.
- Click [Import].
- Choose the encapsulated assertion file to import and then click [Open].
- If there is a conflict with the GUID for the encapsulated assertion, choose an action:
The encapsulated assertion and its underlying policy fragment are imported. If the policy fragment includes references to other entities (for example, JDBC connections or other policy fragments), these are also imported. If conflicts occur, the Resolve External Dependencies Wizard displays.
- Overwrite:Select this to update the existing encapsulated assertion with attributes from the imported assertionexcept for the name, which remains unchanged. The underlying policy fragment of the existing assertion will also be overwritten by fragment associated with the imported encapsulated assertion.
- Create New:Select this to give a new name for the imported encapsulate assertion and its underlying policy fragment. You will be asked to resolve naming conflicts if you enter a name already in use.
- Cancel:Close the dialog box without importing anything.
- Click [Close] when done.