Integration of configruation aware RM service provider with jazz
I have Jazz team server 6.0.1 RC running on a linux machine.
I have implemented my own RM service provider and it is integrated and working fine with jazz quality management module.
Now, I am trying to make my RM service provider "Configuration Aware" on the guidelines given in OSLC Configuration Management 1.0 https://tools.oasis-open.org/version-control/browse/wsvn/oslc-ccm/trunk/specs/config-mgt/oslc-config-mgt.html.
I have associated my jazz qm project with a Global Configuration Context. And now when I try to access my service provider (qm project -> planning (selected a testPlan) -> Requirement Collection Links -> +), jazz gives an error saying that "AQXCM5046E The selected project, "MyProjectName", does not support configuration management capabilities."
Question: What should I do in my rootServices rdf and serviceProvider rdf so that jazz can know that my service provider is Configuration Aware?
I have implemented my own RM service provider and it is integrated and working fine with jazz quality management module.
Now, I am trying to make my RM service provider "Configuration Aware" on the guidelines given in OSLC Configuration Management 1.0 https://tools.oasis-open.org/version-control/browse/wsvn/oslc-ccm/trunk/specs/config-mgt/oslc-config-mgt.html.
I have associated my jazz qm project with a Global Configuration Context. And now when I try to access my service provider (qm project -> planning (selected a testPlan) -> Requirement Collection Links -> +), jazz gives an error saying that "AQXCM5046E The selected project, "MyProjectName", does not support configuration management capabilities."
Question: What should I do in my rootServices rdf and serviceProvider rdf so that jazz can know that my service provider is Configuration Aware?
Accepted answer
Check out this page on the deployment wiki:
https://jazz.net/wiki/bin/view/Deployment/IntegratingWithConfigurationManagementEnabledCLMApplications
There are some service provider parameters that the CLM applications check, especially the configurationAware property. Those are detailed in this section of that wiki page. You may find some other pertinent information there also.
If you have any insights to share based on your experience, we'd like to hear them.
https://jazz.net/wiki/bin/view/Deployment/IntegratingWithConfigurationManagementEnabledCLMApplications
There are some service provider parameters that the CLM applications check, especially the configurationAware property. Those are detailed in this section of that wiki page. You may find some other pertinent information there also.
If you have any insights to share based on your experience, we'd like to hear them.
Comments
2 other answers
Hi Saqib,
I'm not sure I understand your question. But the following might help. In order for the GCM application to be able to select configurations from a CM provider, GCM discovers which CM providers support selection dialogs as follows:
This indicates that the OSLC Service Provider Catalog for CM discovery is at https://localhost:9443/rm/oslc_config
A GET on that should return something like:
A GET on that service provider gives:
Best regards,
David
I'm not sure I understand your question. But the following might help. In order for the GCM application to be able to select configurations from a CM provider, GCM discovers which CM providers support selection dialogs as follows:
- It determines the friends known to the JTS. For example, this might include "/qm", "/rm" and so on.
- For each friend from #1, it gets its root services document. It looks for an oslc_config:cmServiceProvider statement. The object of that statement should be the URI of an OSLC service provider catalog.
- It reads the service provider catalog, and looks at each service provider. Those that declare a selection dialog are noted as available CM providers.
<oslc_config:cmServiceProviders rdf:resource="https://localhost:9443/rm/oslc_config"/>
This indicates that the OSLC Service Provider Catalog for CM discovery is at https://localhost:9443/rm/oslc_config
A GET on that should return something like:
The example RDF shows a service provider at https://localhost:9443/rm/oslc_config/components<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:vvc="http://jazz.net/ns/vvc#"
xmlns:dcterms="http://purl.org/dc/terms/"><oslc:ServiceProviderCatalog> <oslc:serviceProvider>
<oslc:ServiceProvider rdf:about="https://localhost:9443/rm/oslc_config/components">
<oslc:details rdf:resource="https://localhost:9443/rm/oslc_config/components"/>
<dcterms:title>Requirements Management</dcterms:title>
</oslc:ServiceProvider>
</oslc:serviceProvider><oslc:domain rdf:resource="http://open-services.net/ns/config#"/> <dcterms:description>Configuration Services Provided by the RM application.</dcterms:description>
<dcterms:title>RM Configuration Management Services Catalog</dcterms:title>
</oslc:ServiceProviderCatalog></rdf:RDF>
A GET on that service provider gives:
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:vvc="http://jazz.net/ns/vvc#"
xmlns:dcterms="http://purl.org/dc/terms/">
<oslc:ServiceProvider>
<oslc:service>
<oslc:Service>
<oslc:selectionDialog>
<oslc:Dialog>
<dcterms:title>RM Component Configuration Picker</dcterms:title>
<oslc:label>RM Component Configuration Picker</oslc:label>
<oslc:dialog rdf:resource="https://localhost:9443/rm/_ajax-modules/com.ibm.rdm.web.OslcConfigurationPickerPane"/>
<oslc:hintWidth>600px</oslc:hintWidth>
<oslc:hintHeight>500px</oslc:hintHeight>
<oslc:resourceType rdf:resource="http://jazz.net/ns/vvc#Configuration"/>
<oslc:usage rdf:resource="http://jazz.net/ns/vvc#Configuration"/>
</oslc:Dialog>
</oslc:selectionDialog>
</oslc:Service>
</oslc:service>
</oslc:ServiceProvider>
</rdf:RDF>
Hope that helps,
Best regards,
David
Comments
1 vote
Hi Saqib,
The open-services.net namespaces are defined based on the OSLC specifications. You need those as part of implementing the specs.
CLM has implemented some extensions beyond the specifications, like the service provider properties. Those are defined in the jazz.net namespace mentioned.
Does that help?
The open-services.net namespaces are defined based on the OSLC specifications. You need those as part of implementing the specs.
CLM has implemented some extensions beyond the specifications, like the service provider properties. Those are defined in the jazz.net namespace mentioned.
Does that help?