Method and system for implementing a global information bus in a global ecosystem of interrelated services

• US 8,626,877 B2
• Filed: 03/29/2002
• Issued: 01/07/2014
• Est. Priority Date: 05/22/2000
• Status: Active Grant

• Current Assignee: EKMK Limited Liability Company
• Original Assignee: Verizon Business Global LLC (Verizon Communications Inc.)
• Inventors: Greene, William S., Robertson, James A.
• Primary Examiner(s): Pulliam, Christyann
• Assistant Examiner(s): Chojnacki, Mellissa M
• Application Number:
  US10/113,472
• Publication Number:
  US 20030004744A1
• Time in Patent Office: 4,302 Days
• Field of Search: 707 1- 10, 707102-104, 707/203, 707/738, 709/203, 709225-228, 709/220
• US Class Current: 709/220
• 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

A Global Information Bus (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 series of collaborating services may start to resemble an ecosystem, and GIB architecture may 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 group of network domains.

Claims

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

deploying a service in a network domain, the enterprise comprising a plurality of non-local network domains in addition to the network domain, where each network domain is at least partially defined by a multicast radius;

discovering a domain registrar, the domain registrar being in the network domain and where discovery of the domain registrar is based on the multicast radius of the network domain;

registering the service with the domain registrar by passing information related to the service to the domain registrar, said information related to the service being one of location information for the domain registrar in the network domain where the service is registered or an implementation interface, and where said information is only visible to a client in the network;

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

listing the service with the global lookup by passing information related to the service to the global lookup, said information related to the service being visible to a client in the enterprise.

2. The method recited in claim 1, where 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, where launching said service in a container running in the network domain further comprises:

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

fetching said service code based on the location information.

4. The method recited in claim 3 further comprising:

selecting the container running in the network domain.

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

pinging the network domain for the domain registrar; and

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

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

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

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

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

10. The method recited in claim 8, where administrative information comprises one of a display icon or a user interface object.

11. The method recited in claim 1, where 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 domain registrar.

12. The method recited in claim 11, where 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, where 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 in the network domain where the service is registered, or an implementation interface.

14. The method recited in claim 11, where 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 1, where listing the service with the global lookup further comprises passing a proxy reference for the service to the global lookup.

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

finding a service container running in the network domain; and

launching said service in a container service.

17. The method recited in claim 16, where 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 being listed in the global repository.

18. The method recited in claim 16, where launching said service in a container service further comprises:

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

19. 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.

20. The method recited in claim 1 further comprising:

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

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

22. The method recited in claim 21 further comprising:

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

23. The method recited in claim 21 further comprises:

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

de-registering the service with the domain registrar, where the information related to the service at the domain registrar is not visible to a client in the network domain.

24. The method recited in claim 23 further comprising:

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

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

deleting information related to the service from the global lookup.

25. The method recited in claim 24 further comprising:

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, where 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.

26. The method recited in claim 24 further comprising:

deploying another service in a network domain, where 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, where the other service is only visible to a client in the network domain.

27. The method recited in claim 17, where the attribute for the service container listed in said global repository relates to one of resource availability or loading.

28. The method recited in claim 16, where 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.

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

defining a plurality of network domains, each of a plurality of network domains comprising a plurality of host servers, where each of the plurality of network domains is partially defined by a multicast radius;

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, where 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 based on the multicast radius of the first network domain; and

registering a second arbitrary service of the plurality of arbitrary services, where the registering comprises listing the second arbitrary service with a global lookup service that provides enterprise-wide visibility for services listed within the global lookup service, where the second arbitrary service is registered in a second network domain of the plurality of network domains in which the second arbitrary service is running, and where 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.

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

31. The method recited in claim 29, where the first network domain and the second network domain are unique network domains.

32. The method recited in claim 29 further comprising:

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

33. A program product embodied on a non-transitory computer processing system readable medium, having instructions executable by at least one processor, 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, when executed by the at least one processor, cause the processor to;

deploy a service in a network domain, where the enterprise comprises a plurality of network domains and each network domain is at least partially defined by a multicast radius;

discover a domain registrar, where the domain registrar is in the network domain and where discovery of the domain registrar is based in part on the multicast radius of the network domain;

register the service with the domain registrar by passing information related to the service to the domain registrar, where said information related to the service is visible to a client from the domain registrar and comprises a proxy reference for the service, service attributes for the service, location information for the domain registrar in the network domain where the service is registered, or an implementation interface, the service being visible only to a client in the network domain;

find a global lookup in the enterprise, where the global lookup is outside the network domain; and

list the service with the global lookup by passing information related to the service to the global lookup, where said information related to the service is visible to a client in the enterprise.

34. The program product recited in claim 33, where the instructions for deploying a service in a network domain further comprise instructions for launching said service in a container when the container is running in the network domain.

35. The program product recited in claim 34, where the instructions for launching said service in the container running in the network domain, when executed by the at least one processor, cause the processor to:

receive location information for a service code for implementing the service; and

fetch said service code based on the location information.

36. The program product recited in claim 35, further comprising, instructions, when executed by the at least one processor, cause the process to:

select the container running in the network domain.

37. The program product recited in claim 33, where the instructions for discovering a domain registrar in the network domain are performed by the service, when executed by the at least one processor, cause the processor to:

ping the network domain for the domain registrar; and

receive a response from the domain registrar in the network domain, where the response includes location information for the domain registrar.

38. The program product recited in claim 33, where the location information is a Universal Resource Locator (URL) for the domain registrar.

39. The program product recited in claim 37, where said information related to the service passed to the domain registrar is a proxy object for the service.

40. The program product recited in claim 33, where said information related to the service passed to the domain registrar is one of a service attribute or administrative information related to the domain registrar.

41. The program product recited in claim 40, where a service attribute comprises one of service identity information, domain information or an implementing interface.

42. The program product recited in claim 40, where the administrative information comprises one of a display icon or a user interface object.

43. The program product recited in claim 33, where the instructions for finding a global lookup in the enterprise are performed by the service, when executed by the at least one processor, cause the processor to:

look up a location for a global lookup finding service in the domain registrar.

44. The program product recited in claim 43, where the instructions for listing the service with the global lookup, when executed by the at least one processor, cause the processor to:

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

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

45. The program product recited in claim 43, where the instructions for listing the service with the global lookup, when executed by the at least one processor, cause the processor to:

pass location for the global lookup from the global lookup service to the service; and

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

46. The program product recited in claim 45, where 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 in the network domain in which the service is registered, or an implementation interface.

47. The program product recited in claim 33, where the instructions for listing the service with the global lookup, when executed by the at least one processor, cause the processor to:

pass a proxy reference for the service to the global lookup.

48. The program product recited in claim 33, where the instructions for deploying a service in a network domain, when executed by the at least one processor, cause the processor to:

find a service container running in the network domain; and

launch said service in the container service.

49. The program product recited in claim 48, where the instructions for finding a service container, when executed by the at least one processor, cause the processor to:

look 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.

50. The program product recited in claim 48, where the instructions for launching said service in a container service, when executed by the at least one processor, cause the processor to:

pass service code location information for a service code for implementing the service to the service container, where said service container fetches the service code based on the service code location information.

51. The program product recited in claim 33,further comprising instructions, when executed by the at least one processor, cause the processor to:

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

register the additional service with another domain registrar;

find the global lookup in the enterprise; and

list the additional service with the global lookup.

52. The program product recited in claim 33, further comprising instructions, when executed by the at least one processor, cause the processor to:

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

53. The program product recited in claim 52, where the instructions for creating an enterprise lease with the domain registrar, when executed by the at least one processor, cause the processor to:

specify a lease period for the service.

54. The program product recited in claim 52, further comprising instructions, when executed by the at least one processor, cause the processor to:

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

55. The program product recited in claim 53, further comprising instructions, when executed by the at least one processor, cause the processor to:

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

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

56. The program product recited in claim 55, further comprising instructions, when executed by the at least one processor, cause the processor to:

monitor the information related to the service at the domain registrar;

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

delete information related to the service from the global lookup.

57. The program product recited in claim 56, further comprising instructions, when executed by the at least one processor, cause the processor to:

monitor enterprise leases created with the domain registrar;

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

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

discover another domain registrar in the other network domain, where the other network domain is one of the plurality of network domains in the enterprise;

register the service with the other domain registrar;

find the global lookup in the enterprise; and

list the service with the global lookup.

58. The program product recited in claim 56, further comprising instructions, when executed by the at least one processor, cause the processor to:

deploy another service in a network domain, where the enterprise comprises a plurality of network domains;

discover a domain registrar in the network domain; and

register the other service with the domain registrar, where the other service is visible to a client at the domain registrar.

59. The program product recited in claim 49, where the attribute for the service container listed in said global repository relates to one of resource availability or loading.

60. The program product recited in claim 48, where 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.

61. A program product embodied on a non-transitory computer processing system readable medium, having instructions executable by at least one processor, 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, when executed by the at least one processor, cause the processor to;

define a plurality of network domains, each of a plurality of network domains comprising a plurality of host servers, where each of the plurality of network domains is partially defined by a multicast radius;

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

register 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, where 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 based on the multicast radius of the first network domain; and

register 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, where 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, and

where the registering comprises listing the second arbitrary service with a global lookup service that provides enterprise-wide visibility for services within the global lookup service.

62. The program product recited in claim 61, where the first network domain and the second network domain are the same network domain.

63. The program product recited in claim 61, where the first network domain and the second network domain are unique network domains.

64. The program product recited in claim 61, further comprising instructions, when executed by the at least one processor, cause the processor to:

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

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

a first host processor for implementing an enterprise repository for the enterprise, where 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 a plurality of network domains, where the first network domain is at least partially defined by a first multicast radius; and

a second network domain of the plurality of network domains, where the second network domain is at least partially defined by a second multicast radius, comprising;

a second host processor for running a domain registry service for the second network domain, where the domain registry service receives related information for an arbitrary service, where the related information includes a proxy reference for the arbitrary service, service attributes for the arbitrary service, location information for the domain registry service or an implementation interface related to the arbitrary service, where the domain registry service lists the related information for the arbitrary service therein, and where discovery of the domain registry service is based in part on the second multicast radius of the second network domain;

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

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

66. The system recited in claim 65, where 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.

67. The system recited in claim 66 further comprising:

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

a fifth host processor for running a launcher service, where 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.

68. The system recited in claim 67, where the launcher service selects the container service for the arbitrary service based on service attributes of the arbitrary service.

69. The system recited in claim 67, where 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.

70. The system recited in claim 69, where the location information is a Universal Resource Locator (URL) for the domain registrar.

71. The system recited in claim 67, where the related information is a proxy object.

72. The system recited in claim 67, where the related information is one of a service attribute or administrative information.

73. The system recited in claim 72, where a service attribute comprises one of service identity, domain information or implementing interface.

74. The system recited in claim 72, where administrative information comprises one of display icon or user interface object.

75. The system recited in claim 65 further comprising:

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

76. The system recited in claim 75 where 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.

77. The system recited in claim 76, where the related information is one of a proxy reference for the service, service attributes for the service, location information for the domain registry service, or an implementation interface.

78. The system recited in claim 75, where 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.

79. The system recited in claim 65, where the second arbitrary service lists with the enterprise repository by passing a proxy reference for the second arbitrary service to the enterprise repository.

80. The system recited in claim 65, where the third host processor runs a container service and the first arbitrary service launches in the container service.

81. The system recited in claim 80, where the container service lists an attribute in the enterprise repository and the attribute is comparable to the first arbitrary service.

82. The system recited in claim 80 further comprising:

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

a fifth host processor for running a launcher service, where 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.

83. The system recited in claim 65 further comprising:

a fifth host processor for running a second domain registry service for the first network domain, where the second 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, where the third arbitrary service passes related information to the enterprise repository and passes related information to the second domain registry service.

84. The system recited in claim 65, where the domain registry service manages enterprise leases for arbitrary services, and the first arbitrary service creates an enterprise lease with the domain registry service.

85. The system recited in claim 84, where the domain registry service manages enterprise leases for arbitrary services for a specified lease period.

86. The system recited in claim 84, where the first arbitrary service renews the enterprise lease with the domain registry service.

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

88. The system recited in claim 87 further comprising:

a fifth host processor for running a scavenger service, where 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.

89. The system recited in claim 88 further comprising:

a sixth host processor for running a re-starter service for re-starting an arbitrary service, where 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.

90. The system recited in claim 88 further comprising:

a seventh host processor for running a second domain registry service for the first network domain, where the second 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, where the third arbitrary service discovers the second domain registry service, passes related information to the second domain registry service, finds the enterprise repository, and passes related information to the enterprise repository.

91. The system recited in claim 81, where the attribute relates to one of resource availability and loading.

92. The system recited in claim 80, where 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.

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

a plurality of network domains, each of the plurality of network domains comprising a plurality of host servers, the host servers being implemented at least partially in hardware, each of the plurality of network domains being at least partially defined by a multicast radius, where one or more of the plurality of host servers comprising an enterprise repository for registering one or more arbitrary services so that the one or more arbitrary services have enterprise-wide visibility;

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, where 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 based in part on the multicast radius of the 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, where 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.

94. The system recited in claim 93, where the first network domain and the second network domain are the same network domain.

95. The system recited in claim 93, where the first network domain and the second network domain are unique network domains.

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

97. A method for implementing a Global Information Bus (GIB) system for managing a global ecosystem of interrelated services in an enterprise that comprises a plurality of logical domains, the method comprising:

receiving a request for a service from a client in a first one of the plurality of logical domains of the enterprise, where the first one of the plurality of logical domains is at least partially defined by a multicast radius, where the request is received in the first one of the plurality of logical domains and further includes a service identifier for the requested service, and where the service identifier includes an attribute of the service or an interface for the service;

looking up the service identifier in a domain registry for the first one of the plurality of logical domains, where said domain registry lists services registered in the first one of the plurality of logical domains that are only visible to clients in the first one of the plurality of logical domains and not visible to clients outside of the first one of the plurality of logical domains based in part on the multicast radius of the first one of the plurality of logical domains;

receiving an indication that the requested service is not available in the first one of the logical domains;

upon receiving the indication, accessing an enterprise repository for the requested service using the service identifier, where the enterprise repository lists services running in at least two of the plurality of the logical domains of the enterprise, where the list of the enterprise repository is visible to clients of more than one logical domain of the plurality of logical domains of the enterprise; and

returning information related to the requested service to the client.

114. The method of claim 97, where at least one service registered in the first one of the plurality of logical domains is not listed in the enterprise repository, where clients outside of the first one of the plurality of logical domains are not able to access the at least one service registered in the first one of the plurality of logical domains.

115. The method of claim 97, where at least one service registered in the first one of the plurality of logical domains is also listed in the enterprise repository, where clients outside of the first one of the plurality of logical domains are able to access the at least one service registered in the first one of the plurality of logical domains.

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

one or more processors to implement;

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, where each network domain is at least partially defined by a multicast radius, said plurality of services comprising;

a plurality of generic container services for running services, where 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, where 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, where 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, where 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, where 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 domains;

a plurality of transaction management services for creating and managing transactions for services running on a plurality of servers in the plurality of network domains, where the plurality of transaction management services is to create transactions for certain of the plurality of services when the certain of the plurality of services requests one or more transactions; and

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

a plurality of mobile codes for a respective plurality of services, where the 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 services running in the enterprise.

99. The system in claim 98, where 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.

100. The system recited in claim 99, where the launching service receives location information for service code for the service from a health service.

101. The method recited in claim 100, where the location information is a reference to a code server.

102. The method recited in claim 100, where the launching service receives resource information from the health service and selects a container service based on the resource information.

103. The system recited in claim 98 further comprising:

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

104. The system recited in claim 99, where 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.

105. The system recited in claim 104, where 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.

106. The system recited in claim 105, where a service attribute comprises one of service identity information, domain information or an implementing interface.

107. The system recited in claim 105, where administrative information comprises one of a display icon or a user interface object.

108. The system recited in claim 98 further comprising:

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

109. The system recited in claim 99, where 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.

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

111. The system recited in claim 110, where the service and the participant service are set to a state prior to commencement of the transaction by the transaction manager service, where the transaction manager service is related to a transaction process and where the state is based on a failure of one of the services or the participant service prior to a completion of the transaction.

112. The system recited in claim 110, where one of the service or the participant service renews the lease for the transaction to extend the predetermined time to-live for the transaction.

113. The system recited in claim 98, where 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.