Network component server

• US 6,085,030 A
• Filed: 05/02/1997
• Issued: 07/04/2000
• Est. Priority Date: 05/02/1997
• Status: Expired due to Term

• Current Assignee: RPX Corporation
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Christensen, John Darrell, Whitehead, W. Robert
• Primary Examiner(s): Geckil, Mehmet B.
• Application Number:
  US08/850,078
• Time in Patent Office: 1,159 Days
• Field of Search: 395/200.31, 395/200.33, 395/800.28, 395/200.47, 395/200.59, 395/200.49, 395/62, 395/683, 707/10, 707/104
• US Class Current: 709/203
• CPC Class Codes: G06F 2209/462 Lookup
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A component server architecture is provided that enables consumer nodes of a computer network to interact with heterogeneous software components and services distributed throughout the network, as well as network devices and data. Distributed interaction between a consumer and heterogeneous software is achieved, in part, by registering and locating the components and services (hereafter referred to collectively as components). An object-neutral global component registry with access controls of the architecture interoperates with a component management service (CMS) to transparently ensure proper administration, authentication and run-time binding access to components offered in response to requests from applications executing on the consumer nodes. The architecture is implemented on a component server node of the network that is configured to communicate with the consumer, i.e., client, nodes in client-server computing arrangements. That is, the component registry of the component server node responds to a consumer application request by locating a heterogeneous component for the consumer. The registry offers this component to the consumer by providing an appropriate interface between the object model of the consumer and the object model of the software component. This registry is preferably organized as a plurality of cooperating storage entities including a description repository, an offer repository, an interface adapter repository and an object factory repository.

Claims

1. A component server for integrating, exposing and managing distributed components residing on a computer network, comprising:

a component management service for controlling requests for distributed components and services; and

a component registry for accessing registered components and services in response to requests from said component management service, said component registry including,

a description repository for performing an initial look up function based on the type of the request,

an offer repository for receiving the request when the component type is located in said description repository and having instances of components stored therein, an instance of said components being accessed when the instance matches the request,

an object factory repository having implementations of the components registered in said offer repository stored therein, an implementation being invoked corresponding to the component instance accessed by said offer repository, and

an interface adapter repository for storing interface specifications for the implementations stored in said object factory repository, an interface specification being passed to said component management service for the invoked implementation;

said component management service providing the necessary binding between the requested and offered components.

2. A component server according to claim 1, wherein said component management service comprises software for managing the components and services across a plurality of object models, hardware devices, network devices and types of information.

3. A component server according to claim 1, wherein said component registry comprises information for registered components and services so that said component management service may globally register, discover and bind offered components and services to requested components and services which are registered in said component registry.

4. A component server according to claim 1, wherein said component management service further controls authenticated access for registering, discovering and binding of offered components and services.

5. A component server according to claim 1, wherein said component management service further provides a single point of control for managing hardware and embedded devices that discovers and binds requested components and services based on security access controls.

6. A component server according to claim 1, wherein said component management service further provides a single point of control for managing information that discovers and binds requested components and services based on security access controls.

7. A component server according to claim 1, wherein said component management service further provides a single point of control for distributing components and services.

8. A component server according to claim 1, wherein said component management service further provides a single point of control for licensing components and services.

9. A component server according to claim 1, wherein said component management service further provides a single point of control for re-directing requested components and services.

10. A component server according to claim 1, wherein said component management service further provides a single point of control for bridging object models of requested components and services.

11. A component server according to claim 1, wherein the component registry and the component management service operate with CORBA, COM and Java RMI standards for component infrastructures.

12. A component server according to claim 1, wherein the framework for said component registry is based upon NetWare Directory Services (NDS).

13. A component server according to claim 12, wherein NDS provides authentication, replication, distribution, and management for the offered and requested components.

14. A component server according to claim 12, wherein NDS provides a persistent storage and security access control for said component registry.

15. A component server according to claim 1, wherein the framework for said component registry is based upon LDAP, flat file, or ODBC/JDBC databases.

16. A component server according to claim 1, wherein said component management service comprises an interface adapter for transforming the offered component to interface with the requested component.

17. A component server according to claim 1, wherein said component registry functions as a central repository for caching of components and services to local registries for the requested components and services.

18. A component server according to claim 17, wherein said central repository permits mobile computing by the requested components and services.

19. A component server according to claim 1, wherein said component management service performs load balancing for the requested components and services.

20. A system for integrating, exposing and managing distributed components residing on a computer network, comprising:

managing means for controlling requests for distributed components; and

registry means for accessing registered components in response to requests from said managing means, said registry means including,

first means for performing an initial look up function based on the type of the request,

second means for receiving the request when the component type is located in said first means and having instances of components stored therein, an instance of said components being accessed when the instance matches the request,

third means having implementations of the components registered in said second means stored therein, an implementation being invoked corresponding to the component instance accessed by said second means, and

fourth means for storing interface specifications for the implementations stored in said third means, an interface specification being passed to said managing means for the invoked implementation;

said managing means providing the necessary binding between the requested and offered components.

21. A system according to claim 20, wherein said managing means comprises software for managing the components across a plurality of object models, hardware devices, network devices and types of information.

22. A system according to claim 20, wherein said registry means comprises information for registered components so that said managing means may globally register, discover and bind offered components to requested components which are registered in said registry means.

23. A system according to claim 20, wherein said managing means further controls authenticated access for registering, discovering and binding of offered components.

24. A system according to claim 20, wherein the framework for said registry means is based upon NetWare Directory Services (NDS).

25. A system according to claim 20, wherein said managing means comprises adapting means for transforming the offered component to interface with the requested component.

26. A method for integrating, exposing and managing distributed components residing on a computer network, comprising the steps of:

(a) controlling requests for distributed components;

(b) accessing registered components in response to requests from said step (a), said step (b) including the steps of,

(i) performing an initial look up function based on the type of the request,

(ii) receiving the request when the component type is located at said step (i) and having instances of components stored therein, an instance of said components being accessed when the instance matches the request,

(iii) invoking a registered implementation corresponding to the component instance accessed at said step (ii), and

(iv) storing interface specifications for the registered implementations, an interface specification being passed to said step (a) for the invoked implementation; and

(c) providing the necessary binding between the requested and offered components.

27. A method according to claim 26, wherein said step (a) comprises the step of controlling authenticated access for registering, discovering and binding of offered components.

28. A method according to claim 26, wherein said step (a) comprises the step of transforming the offered component to interface with the requested component.

29. A computer readable medium containing executable program instructions for integrating, exposing and managing distributed components residing on a computer network, the executable program instructions comprising the program instructions for:

(a) controlling requests for distributed components;

(b) accessing registered components in response to requests from said step (a), said step (b) including the steps of,

(i) performing an initial look up function based on the type of the request;

(ii) receiving the request when the component type is located at said step (i) and having instances of components stored therein, an instance of said components being accessed when the instance matches the request;

(iii) invoking a registered implementation corresponding to the component instance accessed at said step (ii), and

(iv) storing interface specifications for the registered implementations, an interface specification being passed to said step (a) for the invoked implementation; and

(c) providing the necessary binding between the requested and offered components.

30. A computer readable medium according to claim 29, wherein said step (a) comprises the program instruction for controlling authenticated access for registering, discovering and binding of offered components.

31. A computer readable medium according to claim 29, wherein said step (a) comprises program instruction for transforming the offered component to interface with the requested component.