IP Library Granted Patent US 8,930,942
Granted Patent B2
US 8,930,942 · App. 13/117,115 · Granted Jan 6, 2015

Capability model for deploying componentized applications

Inventors: Scott A. Vorthmann (Saratoga, CA); Daniel J. G. van der Rijn (San Carlos, CA); Mark L. Lambert (Menlo Park, CA); Laurent Domenech (San Jose, CA); Michael J. Kanaley (Palo Alto, CA)
Assignee: TIBCO Software Inc.
G06F8/60
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 8,930,942
App. No.
13/117,115
Filed
May 26, 2011
Granted
Jan 6, 2015
Kind
B2
Examiner
CHEN, QING
Art Unit
2191
USPC
717/177
Abstract

Disclosed are systems and methods deploying a componentized application using a deployment tool to analyze an application to be deployed, where the application depends on at least two or more deployed capabilities that are interrelated, and the deployed capabilities each provide independent functionality. The deployment tool may automatically identify two or more deployed capability providers that provide the two or more deployed capabilities.

Claims (35)

1. A deployment system for deploying an application, comprising:

a processor;

a memory;

a deployment module stored in the memory and executed by the processor, the deployment module operable to:

analyze an application to be deployed to determine at least two or more deployed capabilities that the application depends on, wherein the application comprises one or more components, and wherein the at least two or more deployed capabilities are interrelated and each provides independent functionality; and

automatically search for and identify two or more deployed capability providers that provide the at least two or more deployed capabilities that are interrelated; and

a capability model stored in a data storage element, wherein the capability model stores information relating to an interrelationship between the two or more deployed capability providers, and wherein the two or more deployed capability providers are interrelated dynamically.

2. The deployment system of claim 1 , wherein the two or more deployed capability providers comprise one or more components.

3. The deployment system of claim 1 , wherein a first capability provider is located at a different application layer than a second capability provider.

4. The deployment system of claim 1 , wherein a third capability provider is operable to provide the interrelationship between the two or more deployed capability providers.

5. The deployment system of claim 1 , wherein the capability model comprises:

information about available capability providers in the deployment system and requirements and capabilities of the available capability providers;

information about associations between the available capability providers due to static metadata; and

information about associations between capability providers that accrue dynamically during application deployment.

6. The deployment system of claim 5 , wherein the deployment module is further operable to effect propagation of capabilities using information from the capability model.

7. The deployment system of claim 1 , wherein a new capability provider joining the two or more deployed capability providers provides the interrelationship between the two or more deployed capability providers.

8. The deployment system of claim 7 , wherein the at least two or more deployed capabilities are interrelated via dynamic metadata, and wherein the new capability provider provides the dynamic metadata.

9. A method for deploying an application, comprising:

analyzing, by a deployment tool, an application to be deployed to determine at least two or more deployed capabilities that the application depends on, wherein the application comprises one or more components, and wherein the at least two or more deployed capabilities are interrelated and each provides independent functionality;

automatically searching for and identifying, by the deployment tool, two or more deployed capability providers that provide the at least two or more deployed capabilities that are interrelated; and

storing a capability model in a data storage element, wherein the capability model stores information relating to an interrelationship between the two or more deployed capability providers, and wherein the two or more deployed capability providers are interrelated dynamically.

10. The method according to claim 9 , wherein the two or more deployed capability providers comprise one or more components.

11. The method according to claim 9 , wherein a first capability provider is located at a different application layer than a second capability provider.

12. The method according to claim 9 , wherein a third capability provider is operable to provide the interrelationship between the two or more deployed capability providers.

13. The method according to claim 9 , wherein the capability model comprises:

information about available capability providers in the deployment system and requirements and capabilities of the available capability providers;

information about associations between the available capability providers due to static metadata; and

information about associations between capability providers that accrue dynamically during application deployment.

14. The method according to claim 13 , wherein the method further comprises effecting, by the deployment tool, propagation of capabilities using information from the capability model.

15. The method according to claim 9 , wherein a new capability provider joining the two or more deployed capability providers provides the interrelationship between the two or more deployed capability providers.

16. The method according to claim 15 , wherein the at least two or more deployed capabilities are interrelated via dynamic metadata, and wherein the new capability provider provides the dynamic metadata.

17. Logic for deploying an application, the logic being embodied in a non-transitory computer-readable medium and when executed operable to:

analyze an application to be deployed to determine at least two or more deployed capabilities that the application depends on, wherein the application comprises one or more components, and wherein the at least two or more deployed capabilities are interrelated and each provides independent functionality;

automatically search for and identify two or more deployed capability providers that provide the at least two or more deployed capabilities that are interrelated; and

store a capability model in a data storage element, wherein the capability model stores information relating to an interrelationship between the two or more deployed capability providers, and wherein the two or more deployed capability providers are interrelated dynamically.

Assignments (17)
CHANGE OF NAME Recorded Jul 1, 2026
From: CLOUD SOFTWARE GROUP, INC.
To: CLOUD SOFTWARE GROUP, LLC
Reel/Frame 075874/0220 →
PATENT SECURITY AGREEMENT Recorded Aug 15, 2025
From: CLOUD SOFTWARE GROUP, INC.; CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 072488/0172 →
SECURITY INTEREST Recorded May 24, 2024
From: CLOUD SOFTWARE GROUP, INC. (F/K/A TIBCO SOFTWARE INC.); CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 067662/0568 →
RELEASE AND REASSIGNMENT OF SECURITY INTEREST IN PATENT (REEL/FRAME 062113/0001) Recorded Apr 14, 2023
From: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
To: CITRIX SYSTEMS, INC.; CLOUD SOFTWARE GROUP, INC. (F/K/A TIBCO SOFTWARE INC.)
Reel/Frame 063339/0525 →
PATENT SECURITY AGREEMENT Recorded Apr 14, 2023
From: CLOUD SOFTWARE GROUP, INC. (F/K/A TIBCO SOFTWARE INC.); CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 063340/0164 →
CHANGE OF NAME Recorded Feb 7, 2023
From: TIBCO SOFTWARE INC.
To: CLOUD SOFTWARE GROUP, INC.
Reel/Frame 062714/0634 →
PATENT SECURITY AGREEMENT Recorded Oct 7, 2022
From: TIBCO SOFTWARE INC.; CITRIX SYSTEMS, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 062112/0262 →
PATENT SECURITY AGREEMENT Recorded Oct 7, 2022
From: TIBCO SOFTWARE INC.; CITRIX SYSTEMS, INC.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 062113/0470 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Oct 7, 2022
From: TIBCO SOFTWARE INC.; CITRIX SYSTEMS, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 062113/0001 →
RELEASE REEL 052115 / FRAME 0318 Recorded Oct 3, 2022
From: KKR LOAN ADMINISTRATION SERVICES LLC
To: TIBCO SOFTWARE INC.
Reel/Frame 061588/0511 →
RELEASE (REEL 034536 / FRAME 0438) Recorded Sep 30, 2022
From: JPMORGAN CHASE BANK, N.A.
To: TIBCO SOFTWARE INC.
Reel/Frame 061574/0963 →
RELEASE (REEL 054275 / FRAME 0975) Recorded May 7, 2021
From: JPMORGAN CHASE BANK, N.A.
To: TIBCO SOFTWARE INC.
Reel/Frame 056176/0398 →
SECURITY AGREEMENT Recorded Nov 2, 2020
From: TIBCO SOFTWARE INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 054275/0975 →
SECURITY AGREEMENT Recorded Mar 6, 2020
From: TIBCO SOFTWARE INC.
To: KKR LOAN ADMINISTRATION SERVICES LLC, AS COLLATERAL AGENT
Reel/Frame 052115/0318 →
SECURITY INTEREST Recorded Dec 5, 2014
From: TIBCO SOFTWARE INC.; TIBCO KABIRA LLC; NETRICS.COM LLC
To: JPMORGAN CHASE BANK., N.A., AS COLLATERAL AGENT
Reel/Frame 034536/0438 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 14, 2014
From: DOMENECH, LAURENT
To: TIBCO SOFTWARE INC.
Reel/Frame 033947/0776 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 18, 2014
From: VORTHMANN, SCOTT; VAN DER RIJN, DANIEL J.G.; LAMBERT, MARK L.
To: TIBCO SOFTWARE INC.
Reel/Frame 033340/0681 →
Continuity (2)
Provisional Application 61348722 · May 26, 2010
Related Publication 20120117560A1 · May 10, 2012