Introduction to Custom Actions
You can configure and enforce policies for TIBCO ActiveMatrix® Service Grid using ActiveMatrix® Service Grid Policy Director Governance. ActiveMatrix Service Grid nodes and ActiveMatrix Service Grid engines have embedded governance agents to enforce policies in the same JVM as the services. Policy enforcement for services in third-party containers is achieved using proxy applications deployed in ActiveMatrix Service Grid nodes.
Governance agents intercept service requests, responses, and fault flows and provide these as Policy Enforcement Points (PEPs) for enforcing policies. When you configure policies, the following information is passed on to the Governance Agent:
- The Governed Object for which you want to enforce the policy (service, reference, and so on.)
- The PEP where you want to run the action (Message In Flow, Out flow, Fault flow, and so on.)
- The action and configuration that makes up the policy (authentication, authorization, and so on.)
ActiveMatrix Service Grid Policy Director Governance supports many types of Governed Objects, PEPs, and actions out-of-the-box. To configure the commonly-used combinations of actions (and action configurations), the PEPs for execution, and the Governed Object types, which are applicable, ActiveMatrix Service Grid Policy Director Governance provides many unconventional Policy Templates. The Security and Logging policies in ActiveMatrix Service Grid Policy Director Governance are examples of out of the box templates.
However, there might be occasions when you want a custom action with a custom policy template to run for a given PEP and Governed Object. This document describes how you can create your own action and define the associated templates and User Interface (UI) to add to the palette of available policies in ActiveMatrix Service Grid Policy Director Governance.
For more details on the governance concepts, see TIBCO ActiveMatrix® Service Grid Concepts.