IP Library Granted Patent US 9,195,446
Granted Patent B2
US 9,195,446 · App. 13/457,819 · Granted Nov 24, 2015

Method and registry for enabling the enforcement of design-time policies during runtime in a service-oriented architecture

Inventors: Thorsten Fiebig (Mannheim, DE); Gary Woods (Seeheim, DE); Daniel Adelhart (Bockhorn, DE)
Assignee: SOFTWARE AG
G06F8/60G06F8/20H04L41/0893G06F11/368H04L67/34
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,195,446
App. No.
13/457,819
Granted
Nov 24, 2015
Kind
B2
Abstract

Certain example embodiments relate to computer-implemented methods enabling the enforcement of design-time policies during runtime in a service-oriented architecture (SOA). The SOA includes SOA assets (e.g., web services), and at least one runtime container configured to enforce runtime policies on SOA assets executed therein. Example methods may include: obtaining at least one design-time policy from a SOA registry, the at least one design-time policy applying to SOA assets grouped into a design-time domain; automatically deriving at least one runtime policy from the at least one design-time policy and at least one runtime domain from the design-time domain, the runtime domain indicating at least one runtime container; performing a compatibility check to determine whether the at least one runtime policy is enforceable by the at least one runtime container; and depending on the compatibility check, automatically deploying the at least one runtime policy to the runtime container.

Claims (42)

1. A computer-implemented method for enabling the enforcement of design-time policies during runtime in a service-oriented architecture (SOA),

wherein the SOA comprises a plurality of SOA assets and at least one runtime container, the runtime container being configured to enforce runtime policies on SOA assets executed therein,

the method comprising:

a. obtaining at least one design-time policy from a SOA registry of the SOA, wherein the at least one design-time policy applies to a plurality of SOA assets grouped into a design-time domain;

b. automatically deriving at least one runtime policy from the at least one design-time policy and at least one runtime domain from the design-time domain, the at least one runtime domain indicating at least one runtime container;

c. performing a compatibility check to determine whether the at least one runtime policy can be enforced by the at least one runtime container; and

d. depending on the result of the compatibility check, automatically deploying the at least one runtime policy to the runtime container.

2. The method of claim 1 , wherein the at least one design-time policy defines at least one restriction to be met by the SOA assets within the respective design-time domain.

3. The method of claim 1 , wherein the at least one design-time policy defines at least one restriction to be met by an interaction between two SOA assets from different design-time domains.

4. The method of claim 1 , wherein the design-time policies and/or the runtime policies comprise one or more WS-Policy assertions.

5. The method of claim 1 , wherein the performing of the compatibility check comprises:

obtaining at least one capability definition of the runtime container from the SOA registry; and

comparing the at least one capability definition of the runtime container with a required capability of the runtime-policy.

6. The method of claim 1 ,

wherein the at least one design-time policy is defined in the SOA registry independent of a specific runtime container; and

wherein the compatibility check is performed based on a mapping obtained from the SOA registry, wherein the mapping maps the design-time domain onto at least one runtime domain, the runtime domain comprising the runtime container.

7. The method of claim 1 , further comprising issuing a notification if the at least one runtime policy cannot be enforced by the runtime container.

8. The method of claim 1 , wherein the design-time domain and/or the runtime domain is defined in at least one taxonomy of the SOA registry.

9. A non-transitory computer readable storage medium tangibly storing instructions that, when executed by a computer system including at least one processor and a memory, implements a method in accordance with claim 1 .

10. A SOA registry for enabling the enforcement of design-time policies during runtime in a service-oriented architecture (SOA),

wherein the SOA comprises a plurality of SOA assets, and at least one runtime container, the runtime container being configured to enforce runtime policies on SOA assets executed therein,

wherein the SOA registry comprises:

a. a policy storage, configured to store at least one design-time policy, wherein the at least one design-time policy applies to a plurality of SOA assets grouped into a design-time domain;

b. at least one processor configured to:

automatically derive at least one runtime policy from the at least one design-time policy and at least one runtime domain from the design-time domain, the at least one runtime domain indicating at least one runtime container;

perform a compatibility check to determine whether the at least one runtime policy can be enforced by the at least one runtime container; and

depending on the result of the compatibility check, automatically deploy the at least one runtime policy to the runtime container.

11. The SOA registry of claim 10 , wherein the at least one processor is further configured, in connection with the performing of the compatibility check, to:

obtain at least one capability definition of the runtime container from the SOA registry; and

compare the at least one capability definition of the runtime container with a required capability of the runtime-policy.

12. The SOA registry of claim 10 ,

wherein the at least one design-time policy is defined in the SOA registry independent of a specific runtime container; and

wherein the at least one processor is further configured, in connection with the performing of the compatibility check, to operate based on a mapping obtained from the SOA registry, wherein the mapping maps the design-time domain onto at least one runtime domain, the runtime domain comprising the runtime container.

13. The SOA registry of claim 10 , further comprising at least one taxonomy configured to define the design-time domain and/or the runtime domain.

14. The SOA registry of claim 10 , wherein the at least one processor is further configured to issue a notification if the at least one runtime policy cannot be enforced by the runtime container.

15. A service-oriented architecture (SOA) system, comprising at least one processor, a memory, a SOA registry in accordance with claim 10 , and at least one runtime container.

16. The method of claim 1 , wherein at least some of the SOA assets are web services.

17. The SOA registry of claim 10 , wherein at least some of the SOA assets are web services.

18. The method of claim 1 , wherein at least one design-time policy includes sending a notification of changes in the SOA registry.

19. The SOA registry of claim 10 , wherein at least one design-time policy includes sending a notification of changes in the SOA registry.

20. The method of claim 1 , wherein automatically deriving at least one runtime policy from the at least one design-time policy includes copying the at least one design-time policy, translating the at least one copied design-time policy into the at least one runtime policy by resolving all domain references in the design-time policy into URIs of the at least one runtime container of the at least one derived runtime domain, and creating a relationship between the at least one design-time policy and the corresponding translated at least one runtime policy.

21. The method of claim 1 , further comprises combining, based on WS-Policy specifications, the at least one design-time policy with the at least one derived runtime policy.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 25, 2024
From: SOFTWARE AG
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 069048/0240 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 27, 2012
From: FIEBIG, THORSTEN; WOODS, GARY; ADELHARDT, DANIEL
To: SOFTWARE AG
Reel/Frame 028118/0326 →
Priority Claims (1)
EP 12161454 · Mar 27, 2012 · regional
Continuity (1)
Related Publication 20130262646A1 · Oct 3, 2013