Contents
This document records Implementation Reports for providers and consumers of the OSLC Reconciliation 2.0 specification.
Providers
Product name and version ( TEMPLATE - copy this section, edit and append )
Contact information:
- Contacts: Your Name ( or many names if multiple contacts )
- Product version number ( indicate approximate future release date if not already released )
Details about support:
- OSLC Reconciliation 2.0
- Indicate if you are a provider or consumer
- Describe how you are exploiting the Reconciliation specification
- List any exceptions or partial support
Table of supported capabilities: See ( get spreadsheet from workgroup lead and fill out )
Additional details about support: (not noted in table)
- List any details about your specific implementation that would not be noted in either the section above or in the spreadsheet
Issues:
- List any issue you have with this specification and note how the workgroup wll resolve
Worked well:
- Describe items that worked well during your implementation
IBM Tivoli Monitoring
Contact information:
- Contacts: Clyde Foster, Janet Andersen
- Product version number : v6.3 ( 1Q2013 release date )
Details about support:
- OSLC Reconciliation 2.0
- The Performance Monitoring service provider of IBM Tivoli Monitoring registers ComputerSystem, IPAddress, SoftwareServer, SoftwareModule, Database, and ServerAccessPoint resources with the Registry Services component of Jazz for Service Management on behalf of monitoring agents.
Table of supported capabilities: See File:OSLC_Reconciliation_2.0_Implementation_Report.ods
Additional details about support:
Issues:
- None
Worked well:
IBM Tivoli Application Dependency Discovery Manager
Contact information:
- Contacts: Marek Smet, Marcin Luczynski, Jaroslaw Jurowicz, Jacek Dolega
- Product version number: 7.2.2, 7.2.1 FP4
Details about support:
- OSLC Reconciliation 2.0
- TADDM has two providers: Configuration and Change History
- Both providers create shapes that contain CRTV attributes so they can be merge later on with resources submitted by other providers,
- TADDM does not have its own query capability.
Table of supported capabilities: See File:OSLC_Reconciliation_2.0_Implementation_Report.ods
Additional details about support: (not noted in table)
Issues:
- No issues, however the process of finding common attributes (needed to merge resources) is difficult.
Worked well:
Jazz for Service Management Registry Services
Contact information:
- Contacts: Joe Ross
- Product version number: v 1.1 (GA target is March 2013)
Details about support:
- Implement service providers based on OSLC Reconciliation 2.0
- Reconciliation specification is used to validate incoming data and to create reconciled resource records
- Resource shape syntax has been extended to include identification rules from the reconciliation specification
- Currently don’t support all aspects of OSLC query syntax for all query capabilities.
Table of supported capabilities: See File:OSLC_Reconciliation_2.0_Implementation_Report.ods
Additional details about support:
- Registered resources are reconciled using the identification rules in the reconciliation specification
Issues:
Worked well:
- Creating resource shapes from the specification worked well, and we were able to use those resource shapes perform reconciliation on incoming registration records.
Consumers
Product name and version ( TEMPLATE - copy this section, edit and append )
Contact information:
- Contacts: Your Name ( or many names if multiple contacts )
- Product version number ( indicate approximate future release date if not already released )
Details about support:
- OSLC Reconciliation 2.0
- Indicate if you are a provider or consumer
- Describe how you are exploiting the Reconciliation specification
- List any exceptions or partial support
Table of supported capabilities: See File:OSLC_Reconciliation_2.0_Implementation_Report.ods
Additional details about support: (not noted in table)
- List any details about your specific implementation that would not be noted in either the section above or in the spreadsheet
Issues:
- List any issue you have with this specification and note how the workgroup wll resolve
Worked well:
- Describe items that worked well during your implementation
Contact information:
- Contacts: Liu Jing Qiong
- Product version number: v7.7 (planned for Q3 2013)
Details about support:
Additional details about support: Not applicable
Issues:
- No significant issues that were not addressed by the spec.
Worked well:
- We were looking for retrieving application structure information from multiple products without peer-to-peer integration, and this fit our requirement.
