General and reusable components for defining net-centric application program architectures

• US 6,971,001 B1
• Filed: 05/17/2001
• Issued: 11/29/2005
• Est. Priority Date: 05/17/2001
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services GmbH (Accenture PLC)
• Inventors: Rolfs, Damon Michael
• Primary Examiner(s): Cao, Chun
• Application Number:
  US09/859,765
• Time in Patent Office: 1,657 Days
• Field of Search: 713/1, 713/2, 717/139, 717/170, 709/203, 709/217, 706/50
• US Class Current: 713/1
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 9/4806 Task transfer initiation or dispatching
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A robust toolkit provides facilities that can be assembled in a modular manner to specify the fundamental architecture of a net-centric application. A bootstrapping process assembles various facilities within the architecture. A configuration facility defines an API for getting properties that can be defined in any number of different types of sources. A factory de-couples how a resource is produced from where the resource is used. A selector framework applies standard query language to contexts other than querying a database. A pipeline architecture defines a model view controller-like framework for a processing pipeline. Selectors are used to specify when certain portions of a Web conversation should be made available to a user. An authorization facility associates permissions with a user to specify which portions of an application a user is authorized to use.

Claims

1. A bootstrapping process for declaratively specifying inclusion of and configuration for a plurality of facilities within a net-centric application program architecture, the bootstrapping process including:

declaratively identifying a plurality of facilities to be included within a program architecture that is configured to operate in a networked environment;

declaratively specifying configuration information for the plurality of facilities, wherein the configuration information can specify a plurality of different types of configuration sources accessible within the networked environment; and

producing a corresponding plurality of facilities based upon the declaratively specified configuration information such that the configuration information supports the bootstrapping process by providing facility-specific configuration information.

2. The bootstrapping process of claim 1 further comprising declaratively specifying configuration information for the plurality of facilities in an XML document.

3. The bootstrapping process of claim 1 wherein producing a corresponding plurality of facilities based upon the declaratively specified configuration information comprises specifying a respective facility deployment context for each of the plurality of facilities by executing a corresponding plurality of implementations of a facility bootstrap task API.

4. The bootstrapping process of claim 3 wherein executing a plurality of implementations of the facility bootstrap task API includes extending the bootstrap process by executing an application-specific implementation of the facility bootstrap task API.

5. The bootstrapping process of claim 1 wherein a plurality of the plurality of different types of facility configuration sources are selected from the group consisting of:

a properties configuration source, a database configuration source, an XML file source, and a “

.ini”

file.

6. A toolkit for setting up architecture facilities and for specifying configuration information for a net-centric application program, the toolkit comprising:

a bootstrapping process for setting up application architecture facilities by executing a plurality of facility bootstrap tasks described in an XML facility deployment document; and

a configuration facility for de-coupling, via a plurality of implementations of a configuration source interface, a plurality of configuration sources of different types from a plurality of operations for accessing the plurality of configuration sources of different types.

7. The toolkit of claim 6 wherein a plurality of the plurality of implementations of the configuration source interface are selected from the group consisting of operations for obtaining configuration information from:

a property file source, an XML file source, and a system property source.

8. The toolkit of claim 6 wherein the configuration facility includes an operation for building a configuration environment based upon information obtained from the plurality of configuration sources of different types.

9. The toolkit of claim 8 wherein earlier-specified configuration information takes precedence over later-specified configuration information.

10. The toolkit of claim 8 wherein the configuration environment includes at least one domain including at least one sub-domain wherein information in the sub-domain takes precedence over information in the domain.

11. A toolkit for architecting a net-centric application program, the toolkit comprising:

a facility deployment descriptor document configurable to define facilities for an application program architecture;

wherein the facility deployment descriptor document includes a plurality of elements each indicative of a facility, and a plurality of sub-elements each indicative of components within a respective facility;

wherein each of the elements include tasks that are executable to assemble a corresponding facility, and

wherein each of the sub-elements include tasks that are executable to retrieve components to be included in the corresponding facility.

12. The toolkit of claim 11, further comprising a parse facility deployment descriptor block configured to parse the elements within the facility deployment descriptor document and an execute facility bootstrap tasks block configured to exccute each of the elements that have been parsed.

13. The tool kit of claim 11, wherein the components are retrieved with the sub-elements from sources of components that are identified within the sub-elements.

14. The tool kit of claim 13, wherein the sources of components include at least one of a properties file on a file system, an environment variable within a computer or data within a database or combinations thereof.

15. The tool kit of claim 13, wherein the sub-elements are configured to plug the retrieved components into the corresponding facility to define how the corresponding facility will operate.

16. The tool kit of claim 11, wherein one of the elements is indicative of an application specific facility.

17. The tool kit of claim 11, wherein each of the elements corresponds to a bootstrap task class.

18. The tool kit of claim 11, wherein one of the sub-elements includes a task that is a set value operation.

19. The tool kit of claim 11, wherein one of the sub-elements includes a task that is a get value operation to retrieve components from a source.

20. The toolkit of claim 11, wherein the facility deployment descriptor document is an XML document.

21. The tool kit of claim 11, wherein the elements are indicative of a set of facilities that include at least two of a configuration facility, a factory facility, a life-cycle management facility a logging facility and an authorization facility.

22. The tool kit of claim 11, wherein one of the elements is a configuration bootstrap task that is indicative of a configuration facility, and the components of one of the corresponding sub-elements are retrieved from a configuration source that is identified with said one of the corresponding sub-elements.

23. The tool kit of claim 22, wherein the configuration source is one of a property file source, a XML file source and a system property source.

24. The tool kit of claim 11, wherein one of the elements is a factory bootstrap task that is indicative of a factory facility, and the components of one of the corresponding sub-elements are retrieved from a producer that is identified with said one of the corresponding sub-elements.

25. The tool kit of claim 23, wherein the configuration source is one of a local producer, an EJB producer and an XML activity plan producer.