Policy Definitions and Concepts
The following definitions and concepts are used to describe policies and policy management.
A policy is set of constraints that you can define and apply in TIBCO Business Studio™ to manage and enforce cross-functional requirements within your application such as security, monitoring, and compliance. You can add policies to activities and bindings in a process to influence or alter actions in the process flow.
Policies that are related or perform similar functions are categorized under policy types. Policies that can be applied to the HTTP layer of SOAP, REST, and pure HTTP services are categorized under the HTTP Security policy type. Policies that can be applied to the SOAP layer are categorized under the SOAP Security policy type.
An activity is the individual unit of work in a process. You can add policies to activities to influence or alter actions in a process flow. For more information about activities, refer to the section "Application Development" in the Getting Started guide.
BindingsA binding is used to establish a connection between SOA Services and their consumers. There are two types of binding components:
You can add policies to bindings to manage, modify and secure message exchanges on the consumer side and provider side. For more information about the types of bindings offered in the workspace, refer to the section "Binding" in the Concepts guide.
When you add a policy on an activity or a binding, the relationship you create between the resources is called a policy association. At runtime, policies are enforced on the activities and their associated bindings.
Policies reference shared resources. You can manage and configure shared resources in your workspace. The following table describes shared resources that each policy might reference.
|Basic Credential Mapping|