Method and system for implementing a Global Information Bus in a global ecosystem of interrelated services

• US 20030004744A1
• Filed: 03/29/2002
• Published: 01/02/2003
• Est. Priority Date: 05/22/2000
• Status: Active Grant

• Current Assignee: EKMK Limited Liability Company
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Robertson, James A., Greene, William S.
• Granted Patent: US 8,626,877 B2
• Time in Patent Office: Days
• US Class Current: 705/1
• CPC Class Codes: G06Q 10/063112 Skill-based matching of a person or a group to a task
• CPC Class Codes: G06Q 10/06314 Calendaring for a resource
• CPC Class Codes: G06Q 10/06398 Performance of employee with respect to a job function
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 10/1093 Calendar-based scheduling for persons or groups
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/0661 by reconfiguring faulty entities
• CPC Class Codes: H04L 41/0663 Performing the actions predefined by failover planning, e.g. switching to standby network elements
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5058 Service discovery by the service manager
• CPC Class Codes: H04L 61/4553 Object oriented directories, e.g. common object request broker architecture [CORBA] name server
• 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/102 Entity profiles
• CPC Class Codes: H04L 63/123 : received data contents, e.g. message integrity
• CPC Class Codes: H04L 67/01 : Protocols
• CPC Class Codes: H04L 67/1095 : Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• 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 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/535 : Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/54 : Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: Y10S 707/99931 : Database or file accessing

Abstract

In accordance with an exemplary embodiment of the present invention, a Global Information Bus (GIB) is disclosed as implemented in a global ecosystem of interrelated services. The GIB architecture is an infrastructure for deploying and managing individual services on a global scale. The GIB is a series of services that may change from one execution to another, finding and collaborating with other services dynamically. This system of collaborating services starts to resemble an ecosystem, and the job of the GIB architecture is to maintain the interconnectedness and stability of this ecosystem as it continually changes. To that end, the GIB includes an enterprise repository service for storing related information related to services running in the enterprise where the enterprise consists of a plurality of network domains. The GIB includes a domain registry service running in each domain which lists information related to services running in the respective domains. When a service is launched in one of the enterprise domains, the service discovers a domain registry service for the local domains and registers itself. Then, if the newly-launched service is to be visible to clients running in non-local domains, the newly-launched service finds the enterprise repository service and lists information about the service, such as the location of its domain registry service. Each service runs in container, running on a processor, which may run several different services. The GIB also includes a code server for holding service code and launcher services for receiving location information for the code server in which a service'"'"'s code resides, and fetches the service code and launches the service code for the service based on container service attributes. Services may be of several types, GIB infrastructure services, services that are parts of applications, services that provide access to persistent DataBus objects, services that act as agents representing external entities such as devices, gateways to external (non-GIB) systems and third party services running in the ecosystem.

Claims

1. A data processing system implemented method for implementing Global Information Bus (GIB) system for managing a global ecosystem of interrelated services in an enterprise comprising:

deploying a service in a network domain, wherein the enterprise comprises a plurality of non-local network domains in addition to the network domain;

discovering a domain registrar, wherein the domain registrar is in the network domain;

registering the service with the domain registrar by passing information related to the service to the domain register, wherein said information related to the service is visible to a client from the domain register;

finding a global lookup in the enterprise, wherein the global lookup is outside the network domain; and

listing the service with the global lookup by passing information related to the service to the global lookup, wherein said information related to the service is visible to a client from the global lookup.

2. The method recited in claim 1, wherein deploying a service in a network domain further comprises launching said service in a container running in the network domain.

3. The method recited in claim 2, wherein launching said service in a container running in the network domain further comprises:

receiving location information for service code for implementing the service; and

fetching said service code based on the location information.

4. The method recited in claim 3 further comprises:

selecting the container running in the network domain.

5. The method recited in claim 1, wherein discovering a domain registrar in the network domain is performed by the service and further comprises:

pinging the network domain for a domain registrar; and

receiving a response from a domain registrar in the network domain, wherein the response includes location information for the domain registrar.

6. The method recited in claim 5, wherein the location information is a Universal Resource Locator (URL) for the domain registrar.

7. The method recited in claim 1, wherein said information related to the service passed to the domain register is a proxy object for the service.

8. The method recited in claim 1, wherein said information related to the service passed to the domain register is one of a service attribute and administrative information to the domain registrar.

9. The method recited in claim 8, wherein a service attribute comprises one of service identity information, domain information and implementing interface.

10. The method recited in claim 8, wherein administrative information comprises one of display icon and user interface object.

11. The method recited in claim 1, wherein finding a global lookup in the enterprise is performed by the service and further comprises:

looking up location information for a global lookup finding service in the network domain registrar.

12. The method recited in claim 11, wherein listing the service with the global lookup further comprises:

passing the information related to the service from the service to the global lookup finding service; and

passing the information related to the service from the global lookup finding service to the global lookup.

13. The method recited in claim 12, wherein information related to the service is one of a proxy reference for the service, service attributes for the service, location information for the domain registrar is in the network domain wherein the service is registered, and an implementation interface.

14. The method recited in claim 11, wherein listing the service with the global lookup further comprises:

passing the location information for the global lookup from the global lookup service to the service; and

passing the information related to the service from the service to the global lookup.

15. The method recited in claim 14, wherein information related to the service is one of a proxy reference for the service, service attributes for the service, location information for the domain registrar is in the network domain wherein the service is registered, and an implementation interface.

16. The method recited in claim 1, wherein listing the service with the global lookup further comprises passing a proxy reference for the service to the global lookup.

17. The method recited in claim 1, wherein deploying a service in a network domain further comprises:

finding a service container running in the network domain; and

launching said service in the container service.

18. The method recited in claim 17, wherein finding a service container further comprises:

looking up location information for a suitable service container in a global repository based on an attribute for the service container, said attribute listed in the global repository.

19. The method recited in claim 17, wherein launching said service in a container service further comprises:

passing service code location information for service code for implementing the service to the service container, wherein said service container fetches the service code based on the service code location information.

20. The method recited in claim 1 further comprises:

deploying an additional service in another network domain in the plurality of network domains;

registering the additional service with another domain registrar;

finding the global lookup in the enterprise; and

listing the additional service with the global lookup.

21. The method recited in claim 1 further comprises:

creating an enterprise lease for the service with the domain registrar.

22. The method recited in claim 21 herein creating an enterprise lease with the domain registrar further comprises specifying a lease period for the service.

23. The method recited in claim 2 further comprises:

renewing the enterprise lease for the service with the domain registrar.

24. The method recited in claim 22 further comprises:

determining that the lease period for the enterprise lease lapsed; and

de-registering the service with the domain registrar, wherein the information related to the service at the domain register is not visible to a client at the domain register.

25. The method recited in claim 24 further comprises:

monitoring the information related to the service at the domain register;

determining that the service has been de-registered with the domain registrar; and

deleting information related to the service from the global lookup.

26. The method recited in claim 25 further comprises:

monitoring enterprise leases created with the domain registrar;

determining that the service has been de-registered with the domain registrar;

re-deploying the service in another network domain in the enterprise based on the service being de-registered with the domain registrar;

discovering another domain registrar in the other network domain, wherein the other network domain is one of the plurality of network domains in the enterprise;

registering the service with the other domain registrar;

finding the global lookup in the enterprise; and

listing the service with the global lookup.

27. The method recited in claim 25 further comprises:

deploying another service in a network domain, wherein the enterprise comprises a plurality of network domains;

discovering a domain registrar in the network domain; and

registering the other service with the domain registrar, wherein the other service is visible to a client at the domain registrar.

28. The method recited in claim 18, wherein the attribute for the service container listed in said global repository relates to one of resource availability and loading.

29. The method recited in claim 17, wherein the service container is a generic service container comprising a CPU process executed on a host server into which an arbitrary service is homed at runtime.

30. A data processing system implemented method for implementing Global Information Bus (GIB) system for managing a global ecosystem of interrelated services in an enterprise comprising:

defining a plurality of network domains, each of a plurality of network domains comprising a plurality of host servers;

homing a plurality of arbitrary services on each of the plurality of host servers;

registering a first arbitrary service of the plurality of arbitrary services in a first network domain of the plurality of network domains in which the first arbitrary service is running, wherein the first arbitrary service is visible to a client running within the first network domain and not visible to a client running outside the first network domain; and

registering a second arbitrary service of the plurality of arbitrary services in a second network domain of the plurality of network domains in which the second arbitrary service is running, wherein the second arbitrary service is visible to a client running within the second network domain and visible to a client running outside the second network domain.

31. The method recited in claim 30, wherein the first network domain and the second network domain are the same network domain.

32. The method recited in claim 30, wherein the first network domain and the second network domain are unique network domains.

33. The method recited in claim 30 further comprises:

running a plurality of generic service containers on each of the plurality of host servers, wherein each of the plurality of arbitrary services is homed to a generic service container on each of the plurality of host servers.

34. The method recited in claim 30, wherein registering the second arbitrary service of the plurality of arbitrary services further comprises listing the second arbitrary service with a global lookup service, wherein the global lookup service provides enterprise-wide visibility for services listed therein.

36. The program product recited in claim 35, wherein the instructions for deploying a service in a network domain further comprises instructions for launching said service in a container running in the network domain.

37. The program product recited in claim 36, wherein the instructions for launching said service in a container running in the network domain further comprises:

instructions for receiving location information for service code for implementing the service; and

instructions for fetching said service code based on the location information.

38. The program product recited in claim 37 further comprises:

instructions for selecting the container running in the network domain.

39. The program product recited in claim 35, wherein the instructions for discovering a domain registrar in the network domain is performed by the service and further comprises:

instructions for pinging the network domain for a domain registrar; and

instructions for receiving a response from a domain registrar in the network domain, wherein the response includes location information for the domain registrar.

40. The program product recited in claim 35, wherein the location information is a Universal Resource Locator (URL) for the domain registrar.

41. The program product recited in claim 39, wherein said information related to the service passed to the domain register is a proxy object for the service.

42. The program product recited in claim 35, wherein said information related to the service passed to the domain register is one of a service attribute and administrative information to the domain registrar.

43. The program product recited in claim 42, wherein a service attribute comprises one of service identity information, domain information and implementing interface.

44. The program product recited in claim 42, wherein administrative information comprises one of display icon and user interface object.

45. The program product recited in claim 35, wherein the instructions for finding a global lookup in the enterprise is performed by the service and further comprises:

instructions for looking up a location for a global lookup finding service in the network domain registrar.

46. The program product recited in claim 45, wherein the instructions for listing the service with the global lookup further comprises:

instructions for passing the information related to the service from the service to the global lookup finding service; and

instructions for passing the information related to the service from the global lookup finding service to the global lookup.

47. The program product recited in claim 46, wherein information related to the service is one of a proxy reference for the service, service attributes for the service, location information for the domain registrar is in the network domain wherein the service is registered, and an implementation interface.

48. The program product recited in claim 45, wherein the instructions for listing the service with the global lookup further comprises:

instructions for passing location for the global lookup from the global lookup service to the service; and

instructions for passing the information related to the service from the service to the global lookup.

49. The program product recited in claim 48, wherein information related to the service is one of a proxy reference for the service, service attributes for the service, location information for the domain registrar is in the network domain wherein the service is registered, and an implementation interface.

50. The program product recited in claim 35, wherein the instructions for listing the service with the global lookup further comprises instructions for passing a proxy reference for the service to the global lookup.

51. The program product recited in claim 35, wherein the instructions for deploying a service in a network domain further comprises:

instructions for finding a service container running in the network domain; and

instructions for launching said service in the container service.

52. The program product recited in claim 51, wherein the instructions for finding a service container further comprises:

instructions for looking up location information for a suitable service container in a global repository based on an attribute for the service container, said attribute listed in the global repository.

53. The program product recited in claim 51, wherein the instructions for launching said service in a container service further comprises:

instructions for passing service code location information for service code for implementing the service to the service container, wherein said service container fetches the service code based on the service code location information.

54. The program product recited in claim 35 further comprises:

instructions for deploying an additional service in another network domain in the plurality of network domains;

instructions for registering the additional service with another domain registrar;

instructions for finding the global lookup in the enterprise; and

instructions for listing the additional service with the global lookup.

55. The program product recited in claim 35 further comprises:

instructions for creating an enterprise lease for the service with the domain registrar.

56. The program product recited in claim 55, wherein the instructions for creating an enterprise lease with the domain registrar further comprises instructions for specifying a lease period for the service.

57. The program product recited in claim 55 further comprises:

instructions for renewing the enterprise lease for the service with the domain registrar.

58. The program product recited in claim 56 further comprises:

instructions for determining that the lease period for the enterprise lease lapsed; and

instructions for de-registering the service with the domain registrar, wherein the information related to the service at the domain register is not visible to a client at the domain register.

59. The program product recited in claim 58 further comprises:

instructions for monitoring the information related to the service at the domain register;

instructions for determining that the service has been de-registered with the domain registrar; and

instructions for deleting information related to the service from the global lookup.

60. The program product recited in claim 59 further comprises:

instructions for monitoring enterprise leases created with the domain registrar;

instructions for determining that the service has been de-registered with the domain registrar;

instructions for re-deploying the service in another network domain in the enterprise based on the service being de-registered with the domain registrar;

instructions for discovering another domain registrar in the other network domain, wherein the other network domain is one of the plurality of network domains in the enterprise;

instructions for registering the service with the other domain registrar;

instructions for finding the global lookup in the enterprise; and

instructions for listing the service with the global lookup.

61. The program product recited in claim 59 further comprises:

instructions for deploying another service in a network domain, wherein the enterprise comprises a plurality of network domains;

instructions for discovering a domain registrar in the network domain; and

instructions for registering the other service with the domain registrar, wherein the other service is visible to a client at the domain registrar.

62. The program product recited in claim 52, wherein the attribute for the service container listed in said global repository relates to one of resource availability and loading.

63. The program product recited in claim 51, wherein the service container is a generic service container comprising a CPU process executed on a host server into which an arbitrary service is homed at runtime.

35. A data processing system implemented program product embodied on a processing system readable medium for implementing a method for implementing Global Information Bus (GIB) system for managing a global ecosystem of interrelated services in an enterprise, the program product comprising:

instructions for deploying a service in a network domain, wherein the enterprise comprises a plurality of network domains;

instructions for discovering a domain registrar, wherein the domain registrar is in the network domain;

instructions for registering the service with the domain registrar by passing information related to the service to the domain register, wherein said information related to the service is visible to a client from the domain register;

instructions for finding a global lookup in the enterprise, wherein the global lookup is outside the network domain; and

instructions for listing the service with the global lookup by passing information related to the service to the global lookup, wherein said information related to the service is visible to a client from the global lookup.

64. A data processing system implemented program product embodied on a processing system readable medium for implementing a method for implementing a Global Information Bus (GIB) system for managing a global ecosystem of interrelated services in an enterprise, the program product comprising:

instructions for defining a plurality of network domains, each of a plurality of network domains comprising a plurality of host servers;

instructions for homing a plurality of arbitrary services on each of the plurality of host servers;

instructions for registering a first arbitrary service of the plurality of arbitrary services in a first network domain of the plurality of network domains in which the first arbitrary service is running, wherein the first arbitrary service is visible to a client running within the first network domain and not visible to a client running outside the first network domain; and

instructions for registering a second arbitrary service of the plurality of arbitrary services in a second network domain of the plurality of network domains in which the second arbitrary service is running, wherein the second arbitrary service is visible to a client running within the second network domain and visible to a client running outside the second network domain.

65. The program product recited in claim 64, wherein the first network domain and the second network domain are the same network domain.

66. The program product recited in claim 64, wherein the first network domain and the second network domain are unique network domains.

67. The program product recited in claim 64 further comprises:

instructions for running a plurality of generic service containers on each of the plurality of host servers, wherein each of the plurality of arbitrary services is homed to a generic service container on each of the plurality of host servers.

68. The program product recited in claim 64, wherein the instructions for registering the second arbitrary service of the plurality of arbitrary services further comprises listing the second arbitrary service with a global lookup service, wherein the global lookup service provides enterprise-wide visibility for services listed therein.

70. The system recited in claim 69, wherein the first arbitrary service and the second arbitrary service are launched in a respective first service container running on the third host processor, and the second service container running on the fourth host processor, each of the first service container and the second service container running in the second network domain.

71. The system recited in claim 70 further comprises:

a code server for holding service code for implementing an arbitrary service; and

a fifth host processor for running a launcher service, wherein the launcher service receives location information related to the code server for the service code for the arbitrary service, fetches the service code for the arbitrary service based on the location information and launches the service code for the arbitrary service based on container service.

72. The system recited in claim 71, wherein the launcher service selects the container service for the arbitrary service based on service attributes of the arbitrary service.

73. The system recited in claim 71, wherein the network domain registry service running on the second host processor receives a ping from the first arbitrary service and returns a response, said response including location information for the network domain registry service running on the second host processor.

74. The system recited in claim 73, wherein the location information is a Universal Resource Locator (URL) for the domain registrar.

75. The system recited in claim 71, wherein the related information is a proxy object.

76. The system recited in claim 71, wherein the related information is one of a service attribute and administrative information.

77. The system recited in claim 76, wherein a service attribute comprises one of service identity, domain information and implementing interface.

78. The system recited in claim 76, wherein administrative information comprises one of display icon and user interface object.

79. The system recited in claim 69 further comprises:

a fifth host processor for running a global lookup finding service, wherein the global lookup finding service registers with a domain registrar running in the second network domain, wherein the second arbitrary service looks up a location information for the global lookup finding service in a network domain registrar.

80. The system recited in claim 79 wherein the second arbitrary service passes the related information to the enterprise repository finding service and the enterprise repository finding service passes the related information to the enterprise repository.

81. The system recited in claim 80, wherein the related information is one of a proxy reference for the service, service attributes for the service, location information for the domain registrar, and an implementation interface.

82. The system recited in claim 79, wherein the second arbitrary service receives location information for the enterprise repository from the enterprise repository finding service and passes the related information to the enterprise repository.

83. The system recited in claim 82, wherein related information is one of a proxy reference for the second arbitrary service, service attributes for the service, location information for the domain registrar, and an implementation interface.

84. The system recited in claim 69, wherein the second arbitrary service lists with the enterprise repository by passing a proxy reference for the second arbitrary service to the enterprise repository.

85. The system recited in claim 69, wherein the third host processor runs a container service and the first arbitrary service launches in the container service.

86. The system recited in claim 85, wherein the container service lists an attribute in the enterprise repository and the attribute is comparable to the first arbitrary service.

87. The system recited in claim 85 further comprises:

a code server for holding service code for implementing the first arbitrary service; and

a fifth host processor for running a launcher service, wherein the launcher service receives location information for the code server holding the service code for the first arbitrary service, fetches the service code for the first arbitrary service based on the location information and launches the service code for the first arbitrary service based on the container service.

88. The system recited in claim 69 further comprises:

a fifth host processor for running a second domain registry service for the first network domain, wherein the second network domain registry service receives related information for an arbitrary service and lists the related information therein; and

a sixth host processor for running a third arbitrary service, wherein the third arbitrary service passes related information to the enterprise repository and passes related information to the second network domain registry service.

89. The system recited in claim 69, wherein the domain registry service manages enterprise leases for arbitrary services, and the first arbitrary service creates an enterprise lease with the domain registry service.

90. The system recited in claim 89, wherein the domain registry service manages enterprise leases for arbitrary services for a specified lease period.

91. The system recited in claim 89, wherein the first arbitrary service renews the enterprise lease with the domain registry service.

92. The system recited in claim 90, wherein the domain registry service determines that the lease period for the enterprise lease lapsed and de-registers the first arbitrary service, wherein the related information held in the first registry service is deleted.

93. The system recited in claim 92 further comprises:

a fifth host processor for running a scavenger service, wherein the scavenger service monitors enterprise leases created in the domain registry service, determines that an arbitrary service has been de-registered with the domain registry service and deletes related information for the arbitrary service from the enterprise repository.

94. The system recited in claim 93 further comprises:

a sixth host processor for running a re-starter service for re-starting an arbitrary service, wherein the re-starter service monitors enterprise leases created in the domain registry service and determines that an arbitrary service has been de-registered with the domain registry service, and then re-starts the arbitrary service.

95. The system recited in claim 93 further comprises:

a seventh host processor for running a second domain registry service for the first network domain, wherein the second network domain registry service receives related information for an arbitrary service and lists the related information therein; and

an eighth host processor for running a third arbitrary service, wherein the third arbitrary service discovers the second logical domain registry service, passes related information to the second network domain registry service, finds the enterprise repository, and passes related information to the enterprise repository.

96. The system recited in claim 86, wherein the attribute relates to one of resource availability and loading.

97. The system recited in claim 85, wherein the service container is a generic service container comprising a CPU process executed on a host server into which an arbitrary service is homed at runtime.

69. A system for implementing a Global Information Bus (GIB) for managing a global ecosystem of interrelated services in an enterprise, comprising:

a first host processor for implementing an enterprise repository for the enterprise, wherein the enterprise repository receives related information for an arbitrary service and lists the related information therein for a client in the enterprise;

a first network domain of the plurality of network domains; and

a second network domain of the plurality of network domains comprising;

a second host processor for running a domain registry service for the second network domain, wherein the domain registry service receives related information for an arbitrary service and lists the related information therein;

a third host processor for running a first arbitrary service, wherein the first arbitrary service discovers the network domain registry service and passes related information to the network domain registry service; and

a fourth host processor for running a second arbitrary service, wherein the second arbitrary service discovers the network domain registry service, passes related information to the network domain registry service, finds the enterprise repository, and passes related information to the enterprise repository.

98. A data processing system for managing a global ecosystem of interrelated services in an enterprise comprising:

a plurality of network domains, each of a plurality of network domains comprising a plurality of host servers;

a plurality of arbitrary services homed on each of the plurality of host servers;

a first arbitrary service of the plurality of arbitrary services in a first network domain of the plurality of network domains in which the first arbitrary service is running, wherein the first arbitrary service registers in the first network domain and becomes visible to a client running within the first network domain and not visible to a client running outside the first network domain; and

a second arbitrary service of the plurality of arbitrary services in a second network domain of the plurality of network domains in which the second arbitrary service is running, wherein the second arbitrary service registers in the second network domain and becomes visible to a client running within the second network domain, and lists in the enterprise and becomes visible to a client running outside the second network domain in the enterprise.

99. The system recited in claim 98, wherein the first network domain and the second network domain are the same network domain.

100. The system recited in claim 98, wherein the first network domain and the second network domain are unique network domains.

101. The system recited in claim 98, wherein on each of the plurality of host servers runs a plurality of generic service containers, wherein each of the plurality of arbitrary services is homed to a generic service container on each of the plurality of host servers.

102. The system recited in claim 98 further comprises:

enterprise repository service homed on a server for registering the second arbitrary service of the plurality of arbitrary services, wherein the enterprise repository service provides enterprise-wide visibility for the second arbitrary service listed therein.

103. A data processing system implemented method for implementing a Global Information Bus (GIB) system for managing a global ecosystem ol interrelated services in an enterprise comprising:

receiving a request for a service from a client, wherein the request is received in a logical domain and further includes a service identifier for the requested service;

looking up the service identifier in a domain registry for the logical domain, wherein said domain registry lists services registered in said logical domain;

accessing an enterprise repository for the requested service using the service identifier, wherein said enterprise repository lists services running in said enterprise; and

returning information related to the requested service to the client.

104. The method recited in claim 103, wherein said service identifier is an attribute of the service.

105. The method recited in claim 103, wherein said service identifier is an interface for the service.

106. A data processing system implemented in a Global Information Bus (GIB) system for managing a global ecosystem of interrelated services in an enterprise comprising:

a plurality of services running in the enterprise, the enterprise comprising a plurality of network domains and at least one of the plurality of services running in each of the plurality of network domains, said plurality of services comprising;

a plurality of generic container services for running services, wherein each of the plurality of generic container services is running on a server in one of the plurality of network domains;

a plurality of domain registrar services for registering services running on a server in one of the plurality of network domains, wherein at least one of the plurality of domain registrar services is running in each of the plurality of network domains for registering services running in the each of the respective plurality of network domains;

a plurality of health services for monitoring and responding to changes in the health of a service, wherein at least one of the plurality of health services is running in each of the plurality of network domains;

a plurality of loader services for loading service code to a server in a network domain from a remotely located code server, wherein each of the plurality of loader services responds to communications from a health service with respect to changes in the health of a service;

a plurality of trawler services, wherein each of the trawler services trawls a domain registrar service from the plurality of domain registrar services for information regarding changes in services running in the respective plurality of network domains;

a plurality of scavenger services for receiving information regarding changes in services running in the respective plurality of network domains from at least one of the plurality of trawler services and updating information related to at least some of the plurality of services running in the enterprise with the information regarding changes in services running in the respective plurality of network domain;

a plurality of transaction management services for creating and managing a transactions for services running on a plurality of servers in the plurality of network domains; and

a plurality of find services for finding components of the enterprise;

a plurality of mobile codes for a respective plurality of services, wherein plurality of mobile codes reside on a code server; and

a global lookup for storing information related to at least some of the plurality of 38 services running in the enterprise.

107. The system in claim 106, wherein a service is deployed in a generic container service running on a server in one of the plurality of network domains by a loader service loading service code for the service in the generic container service from a remotely located code server.

108. The system recited in claim 107, wherein the launching service receives location information for service code for the service from a health service.

109. The method recited in claim 108, wherein the location information is a reference to a code server.

110. The method recited in claim 108, wherein the launching service receives resource information from the health service and selects a container service based on the resource information.

111. The system recited in claim 106 further comprises:

a plurality of messaging services for communicating between services running on servers in the plurality of network domain.

112. The system recited in claim 107 wherein the service deployed in the generic container running on a server in one of the plurality of network domains discovers at least one of the plurality of domain registrar services and the at least one of the plurality of domain registrar services is running on a server in a network domain common to the one of the plurality of network domains for the container.

113. The system recited in claim 112, wherein the service passes information related to one of a service attribute and administrative information to the at least one of the plurality of domain registrar services.

114. The system recited in claim 113, wherein a service attribute comprises one of service identity information, domain information and implementing interface.

115. The system recited in claim 113, wherein administrative information comprises one of display icon and user interface object.

116. The system recited in claim 106 further comprises:

a plurality of arbitrary resource services, wherein each of the plurality of arbitrary resource services provides resource support for service running in the enterprise.

117. The system recited in claim 107, wherein the service deployed in the generic container running on a server in one of the plurality of network domains finds a global lookup by looking up location information for a global lookup finding service in one of the plurality of domain registrar services.

118. The system recited in claim 106, wherein a service requests a transaction with a participant service by requesting one of the plurality of transaction management services create a transaction.

119. The system recited in claim 118, wherein the one of the plurality of transaction management services issues a lease for the transaction, wherein the lease defines a predetermined time-to-live for transaction.

120. The system recited in claim 119, wherein the service and the participant service are instructed by the transaction manager service to a transaction process to a state prior to commencement of the transaction based on a failure of one of the services and the participant service prior to a completion of the transaction.

121. The system recited in claim 119, wherein one of the service and the participant service renews the lease for the transaction thereby extending the predetermined time-to-live for the transaction.

122. The system recited in claim 106, wherein registering services running in the each of the respective plurality of network domains further comprises passing proxy objects for the services to the at least one of the plurality of domain registrar services for services running in each of the respective plurality of network domains.