Where's the data? The Jazz SM Registry knows...
joe_ross 110000EJS1 Comments (2) Visits (6463)
If I have multiple products deployed in an IT environment, I can use each of them individually. However, solving a problem often requires access to information from multiple products. For example, if I have a problem with a business application, I might need information about which servers and associated hardware and software support that application. I might then want to know details about how those servers are configured, which of them are overloaded, which ones have had recent configuration changes, and if there are error events being generated for some of them. All of this information might be available from one or more of the products, but accessing all of this information in the context of a specific problem requires that I know which products can provide which kinds of information and links to the specific information that I'm interested in. Jazz SM Registry Services is designed to solve this problem, so that a collection of products can be used to solve problems in an integrated way, as if they were a single tool.
Registry Services is based on the Open Services for Lifecycle Collaboration (OSLC) approach to loosely coupled integration using Linked Data, and it serves as the hub for integration of OSLC data providers and consumers. Registry Services actually consists of two different registries: the Provider Registry and the Resource Registry.
The Provider Registry is a directory of OSLC Service Providers. It is similar in concept to the telephone "yellow pages". When provider products are deployed, they add provider records to the Provider Registry and consumers search the Provider Registry for providers of specific kinds of information or servies. So, the Provider Registry is a container of OSLC Service Provider records, categorized by the domain they operate in and the types of data that they manage.
The Resource Registry is an index to data about resources managed or tracked by multiple providers. Provider products add records to the resource registry for resources that they manage or track in their OLSC Service Providers. These records include identifying properties about the resources like serial numbers, asset tags or hostnames, as well as URLs that point to the data about the resources in the providers. Data consuming products use the resource registry in the same way that a user might use a web search engine. They search for resources that match some search criteria, and the registry provides a list of all of the URLs that can be accessed to obtain additional information about those resources. A key point is that the Resource Registry is not the repository for the data, but an index to the data.
This is just a very brief introduction to Registry Services, so please return to this blog for details about how the Registry works and how it can be used. Also, please feel free to comment and suggest specific topics that you'd like more information about.