International Business Machines Corporation

Lenovo (singapore) Pte. Ltd.

Thomas Charles Burke

Mario Ernesto De Armas

Oswaldo Gago

Maria Elena Smith

Gaurang Shah

Ramon M Spence

Eric Richard Kern

Richard Alan Dayan

Srinivasan Muralidharan

Daryl Carvis Cromer

Randall Scott Springfield

William Joseph Piazza

David Benson Rhoades

William Gavin Holland

Gregory Brian Pruett

Antonio Abbondanzio

Gregory William Dake

Aravind Srinivasan

Annapureddy S Reddy

At least one set of enforceable policy provisions is identified within at least one defined service level policy to be enforced during runtime by a policy enforcement point (PEP). Each set of enforceable policy provisions includes a policy subject, a reference to a policy domain, and at least one assertion. Each identified set of enforceable policy provisions is transformed by the PEP into at least one runtime-executable processing rule that each includes at least one PEP processing action that each represents an atomic unit of policy enforcement level behavior executable by the PEP to enforce the respective at least one assertion against runtime objects associated with the policy subject within an area of runtime policy enforcement specified by the policy domain.

Dynamic generation of policy enforcement rules and actions from policy attachment semantics

A set of service level agreement (SLA) policies and service level definition (SLD) policies that are applied to a request message of a correlated request/response message pair are tracked. A response message of the correlated request/response message pair is detected. A corresponding set of platform-specific policy enforcement processing rules that are used to enforce the set of SLA policies and SLD policies on the response message are identified using the tracked set of SLA policies and SLD policies applied to the request message. The set of SLA policies and SLD policies are enforced on the response message using the identified corresponding set of platform-specific policy enforcement processing rules.

Symmetric coherent request/response policy enforcement

Source policy identification information of a registry service policy is correlated with configured policy enforcement processing rules and processing actions using a source policy reference key. The source policy identification information includes at least a source policy identifier (ID) of the registry service policy. Per-transaction service policy enforcement information that documents policy enforcement activities performed by a policy enforcement point (PEP) is correlated with the source policy identification information using the source policy reference key. The correlated per-transaction service policy enforcement information of at least one transaction from the per-transaction service data table is provided in response to a query from a policy monitoring point (PMP).

Instrumentation and monitoring of service level agreement (SLA) and service policy enforcement

A peer policy object named with a policy enforcement metric context identifier is created at a first policy enforcement point (PEP) platform of a group of peered PEP platforms. The peer policy object uniquely identifies a registered service policy to be enforced during runtime as a shared runtime policy enforcement activity by the group of peered PEP platforms within a peered policy enforcement deployment. The peer policy object named with the policy enforcement metric context identifier is deployed to at least one other peered PEP platform within the peered policy enforcement deployment to initiate the shared runtime policy enforcement activity by the group of peered PEP platforms. At least one runtime policy enforcement metric associated with runtime enforcement of the registered service policy is shared with the at least one other peered PEP platform during runtime using the policy enforcement metric context identifier.

Applying policy attachment service level management (SLM) semantics within a peered policy enforcement deployment

Source policy identification information of a registry service policy is captured. The source policy identification information includes a source policy identifier (ID), a source policy name, and a source policy uniform resource locator (URL). The captured source policy identification information is correlated with configured policy enforcement processing rules and processing actions using a source policy reference key. Per-transaction service policy enforcement information that documents policy enforcement activities performed by a policy enforcement point (PEP) is captured. The captured per-transaction service policy enforcement information is correlated with the captured source policy identification information using the source policy reference key.

At least one defined service policy to be enforced by a policy enforcement point (PEP) is obtained. The obtained at least one defined service policy is parsed to identify at least one set of enforceable policy provisions and the at least one set of enforceable policy provisions is identified. Each set of enforceable policy provisions includes a policy subject, a policy domain, and at least one assertion as the enforceable policy provisions within the at least one defined service policy. At least one runtime processing rule including at least one processing action usable by the PEP is created to enforce the policy subject, the policy domain, and the at least one assertion of each identified at least one set of enforceable policy provisions.

Growing community of inventors

Durham, NC, United States of America

Thomas Charles Burke