
with Tags:
reconciliation
X

Integration scenarios as input to OSLC specifications
A common requirement from the integration scenarios that I've been introducing to you is the need for combining data from multiple sources. For example, while scenario “Service and Application Problem Diagnosis” calls for being able to determine the impact on services and applications of supporting resources and scenario “Deployment of VM, System and Application patterns in Cloud” calls for being able to provision servers in the Cloud, the implementors of both scenarios share the need to process data from diverse inputs such as ... [More]
Tags:  oslc linked_data linked-data tuan ibm-blog-l3 integration scenario reconciliation |
Now you can see Registry Services by the DASHboard Light
There is beauty in visualization, there is paradise in beautiful integration, then there is a Meat Loaf-esque attempt at tying this entry’s title to the intro. For the past two years we have been focusing on consolidating and correlating data from different data providers, and during that time we also put out a rather polished Registry Services Sample UI console that allowed people to browse data stored in Registry Services. All the while we kept throwing a long look across the hallway - actually they sit on the floor above, their not so... [More]
Tags:  dashnoard rest oslc linked_data registry_services ibm-blog-l3 dash resources registry-services dashboarding reconciliation rsotg linked-data nastacio registry dashboard lifecycle |
Technology preview of Asynchronous Reconciliation in Registry Services
The registration of a large number of resources may take days to complete. A large part of this time (up to 40%, depending on the complexity of your data) is used for the reconciliation of the resources. One way to speed the registration is to perform the reconciliation of the resources asynchronously, in a separate task that is independent of the registration itself. Another additional benefit of asynchronous reconciliation, also called continuous reconciliation, specially during bulk-load operations, is that we avoid conflicts and retries... [More]
Tags:  ibm-blog-l3 reconciliation registry-services shape continuous asynchronous resource registry cleansing |
Useful queries to troubleshooting reconciliation issues in Registry Services
*Co-authored and reviewed by Maristela Salvatore @soaresm When sending Registration Records requests to Registry Services, you can find a situation where the reconciled Resource Record was not created or the Registration Record information was not part of an existing reconciled Resource Record. How to figure out why your Registration Records were not reconciled? It might not be easy to find out what could have caused the reconciliation problem, as there is not a straightforward answer for this question. Instead, you can try to understand to... [More]
Tags:  reconciliation registry-services oslc ibm-blog-l3 query |
The Hitchhiker’s Guide to interfacing with Registry Services – Part 2: Queries
In part 1 of this entry , I outlined the concepts and steps required to get data inside Registry Services. I also revealed Registry Services’ party trick, which lies in its ability to recognize seemingly disjoint information from different sources as representing the same entity in the outside world. It has been enough days to let you build that first application, at which point you must be wondering “How do I read that collection of reconciled resource records? Where do I start?” Collections, collections, collections… Sorry about the riff on... [More]
Tags:  reconciliation registry-services paginated specifications hhgirs oslc jazzsm ibm-blog-l3 rdf provider nastacio service-provider query standards resources open-services registry_services registry |
The Hitchhiker’s Guide to interfacing with Registry Services – Part 1: Registration
Business partners and internal development teams often commend the simplicity of the OSLC integration model adopted in Jazz for Service Management, which is based on well-established open web standards. The openness guarantees that the knowledge is reusable in other implementations, and that vendor neutrality will ensure the stability of APIs and the simplicity of integration with other applications. At the same time, those standards do carry a handful of concepts and models on their backs, but do not panic, they are mostly harmless. The... [More]
Tags:  oslc jena registry-services standards nastacio jazzsm linked-data resources service-provider linked_data registry_services open-services hhgirs ibm-blog-l3 tips reconciliation registry specifications rdf |