Introduction to Custom Actions
You can configure and enforce policies for ActiveMatrix using TIBCO ActiveMatrix Policy Director Governance. ActiveMatrix nodes and ActiveMatrix 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 Nodes.
Governance Agents intercept service requests, response, 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 you want to enforce the policy for (Service, Reference, and so on.)
- The PEP you want to execute the action in (Message In Flow, Out flow, Fault flow, and so on.)
- The action and configuration that makes up the policy (Authentication, Authorization, and so on.)
Out-of-the-box, ActiveMatrix Policy Director Governance supports many types of Governed Objects, PEPs, and Actions. To configure commonly used combinations of actions (and action configurations), the PEPs for execution, and the Governed Object types they are applicable, ActiveMatrix Policy Director Governance provides many out-of-the-box Policy Templates. The Security and Logging policies in ActiveMatrix 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 execute 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 TIBCO ActiveMatrix Policy Director Governance.
For more details on the Governance concepts, refer to the TIBCO ActiveMatrix Service Grid Concepts guide.