I am integrating the oslc-adapter producer application with ibm-Jazz/DNG for RM module. After configuring the friend out bound connection in JAZZ-JTS server. I was trying to link the reference’s from DNG-RM module to my adapter while doing this reference from IBM-DNG, I was facing the error
CRRRW7387E The action cannot be completed because an invalid global configuration was specified. To perform this action, you must be working in a valid global configuration. Select a global configuration that includes the RM component you are working with and try the action again.
Please ask the question properly so that people can understand it. Please edit your post to describe what is the problem, what did you try to do, and what did not work.
@jamsden and Nick should know best how to deal with this.
From what I see, you need to add an extra triple to the ServiceProvider definition to declare it GCM-aware. This is how to do it on a new ServiceProvider instance:
final ServiceProvider serviceProvider = new ServiceProvider();
final QName jfsProc_globalConfigurationAware = new QName(
"http://jazz.net/xmlns/prod/jazz/process/1.0/",
"globalConfigurationAware",
"jfs_proc");
serviceProvider
.getExtendedProperties()
.put(jfsProc_globalConfigurationAware, "compatible");
Now, where to add this code is a tricky question. I assume you are using Lyo Designer to generate an RM adaptor? If so, you should look into the xyz.servlet.ServiceProviderCatalogSingleton#createServiceProvider method and add this property before returning the newly created SP. @jad might have a better idea about this.
@jamsden @jad
After adding this extended Properties I am able to see the RDF response as follows But still I am facing the same issue , Help on this to overcome the Global configurations issue with DNG/JTS integration
I’m not sure exactly what your issue is. If your an OSLC client attempting to connect to a DNG project area that is config-enabled, then you need to provide a Configuration-Context HTTP header with the value of the local or global configuration URL describing which version of the resources you want.
Specifying config aware information in the service provider is something a server does that a client might use.
@jamsden
If your an OSLC client attempting to connect to a DNG project area that is config-enabled
–yes @then you need to provide a Configuration-Context HTTP header with the value of the local or global configuration URL describing which version of the resources you want
Could you provide some sample code to retrieve the GC present in DNG and setting to HTTP Header
@andrew
Hi Andrew
it’s working after doing this extra triple to service provider
but some times failing with some other RM-Projects present in DNG by showing error message
“CRRRW7359W The selected component cannot be shown in the current global configuration. Check that the current global configuration is correct and that a configuration for the component exists in the global configuration”
Technical Scenario : I am integrating a External RM-OSLC adapter with DNG-6.0.6
Workflow Working DNG Version-6.0.6
After Configuring the Friend outbound connection and other required configurations to intercommunicate between DNG and External RM-OSLC adapter
I am able to link the references with External RM-project with out GC-configurations RM-Project as well as with GC-configurations enabled RM-PROJECT in DNG
All workflows working fine between DNG-6.0.6 and External RM-OSLC adapter
Workflow NOT Working DNG Version-6.0.6 (CLM_server_patch_6.0.6.0-iFix009-CALM606M-I20190513-0639)
after upgrading DNG-6.0.6 version with IFIX009 Patch updates
I am able to link the references with External RM-project with out GC-configurations RM-Project
But If I do the GC-configurations to DNG-RM project, RM Project having Global configurations
I am Unable to link the references with External RM-project with GC-configurations RM-Project
workflows Not working fine between DNG-6.0.6-IFIX009 RM Project having GC-configurations and External RM-OSLC adapter
Workflow to link the references
RM project having GC-configurations ,it’s showing following exception
“CRRRW7359W The selected component cannot be shown in the current global configuration. Check that the current global configuration is correct and that a configuration for the component exists in the global configuration”
@jamsden Please Provide help/Guidelines to overcome the issue with GC-configurations
If you rely on synchronization or OSLC integrations to relate data in ELM project areas to data in tools that do not support the OASIS OSLC Configuration Management specification, defer enabling configuration management for those project areas until those integrations are supported.
Links to tools outside of ELM are inconsistent until those integrations are updated to be compatible with configuration-enabled projects. This includes IBM tools, tools from other vendors, and custom OSLC integrations, such as those created by using the SDK from the Eclipse Lyo project."
Also take a look at the considerations in the RM section of that document to understand what works and does not work when enabling configuration management for a DNG project area.
It seems OSLC specifications not comptable with the Global configurations of IBM-DNG project area
so OSLC specification have to enhance to adapt the GC specification’s of IBM-DNG (untill oslc application integration will not work with IBM-DNG projects) @andrew @jamsden @jad
Any inputs or guidelines on this
defer enabling configuration management for those project areas until those integrations are supported
I fully agree with that. That’s why it is enabled explicitly with a property in the first place!
Links to tools outside of ELM are inconsistent until those integrations are updated to be compatible with configuration-enabled projects.
This is expected.
This includes IBM tools, tools from other vendors, and custom OSLC integrations, such as those created by using the SDK from the Eclipse Lyo project.
This is basically all OSLC systems. It does not depend how the system was developed, but whether it supports configuration management properly.
It seems OSLC specifications not comptable with the Global configurations of IBM-DNG project area.
The OSLC CfgM specification has not yet been finalised yet. But I expect it to provide such compatibility once it becomes a standard. @jamsden, please correct me if needed.
OSLC specification have to enhance to adapt the GC specification’s of IBM-DNG
I don’t there plans at the moment to standartise all the features of IBM-DNG in OSLC. Any requirements by jfs_proc domain shall be implemented separate from what is in the OSLC.
