Creating Policies
To create a policy
1. Open Software AG Designer and display the CloudStreams Development perspective.
2. In the CloudStreams Governance view, expand your CloudStreams Governance project folder, right-click the Policiesfolder and click New Policy.
3. In the New Policy wizard, complete the following fields.
Option | Description |
CloudStreams Project | Click Browse and select the CloudStreams project in which to create the policy. Select a CloudStreams Governance project if the policy is for a virtual service or a Connector Virtual Service, or select a CloudStreams Provider project if the policy is for a custom cloud connector. |
Name | A name for the new policy. A policy name can contain any character, including spaces. Note: | If you want to change the policy name after it has been created, right-click the service name in the Policies folder and select Rename. |
|
Service Type | Specify whether the policy will be applied to a virtual service or to a Connector Virtual Service. |
Description | Optional. A description for the new policy. This description appears when a user displays a list of policies in the user interface. |
4. Click Next.
5. Click the button next to the Criteriafield to apply the policy to services that meet certain criteria. In the Criteria dialog box that appears, specify the criteria as follows:
a. In the Criteria field, specify a value (SOAP or REST) for the Service Type attribute. That is, specify whether the policy should apply to SOAP services or REST services.
b. Click the plus button next to the Criteria field to add a new row, and choose another criteria attribute (Name or Description) and choose an operator and value for it. For example, specify whether the policy should apply to all SOAP services that are equal to, or start with, or contain the prefix Abc_.
c. Repeat step 2 if desired to specify additional criteria.
d. If you specify multiple criteria, use the Condition field to connect the criteria by the AND or OR operator. The default operator is AND.
Notes:
If you specify no criteria, the policy will apply to all virtual services or connector virtual services (based on your selection in the wizard).
Caution:
CloudStreams checks for policy conflicts when you deploy a virtual service. If the service has only one policy applied to it (that is, the policy you are applying here), that policy will be deployed to
CloudStreams, and
CloudStreams executes the policy's actions in the order in which they are specified in the policy. However, if the service has multiple policies applied to it, a policy conflict might occur. A policy conflict might have unintended consequences.
CloudStreams will warn you of policy conflicts. For more information, see
What Happens When You Deploy a Service?.
6. In the policy editor, click Add Action and select the first action to include in the policy.
Some actions have input parameters, which are displayed in the Action Values section of the editor. For example, the Identify Consumer action has the parameter Anonymous Usage Allowed.
7. Specify values for the input parameters (if any) displayed in the Action Values section.
8. Right-click the action name in the Applied Actions list. Some actions have additional parameters you can select. For detailed descriptions of all policy action parameters, see The Policy Action Reference. 9. Select another action to include in the policy, if desired.
Note: | Make sure to select the actions in the order in which you want them to run when the policy is enforced. You cannot change the order of the actions after you add them; you can only delete them and then add a new list of actions. |
10. Activate the policy when you are ready to put it into effect by right-clicking the policy name in the Policiesfolder and clicking Active. You will not be allowed to activate the policy unless all of its action parameters have been set. If the activation is successful, the value of the Statusfield in the Properties view will change to Active.
When you deploy the virtual services or Connector Virtual Services to which the policy is applied, the policy will be deployed as well.
