Missing Clearcase synchronizer license on CLM 3.0
This is actually a question I got from a prospective customer that's evaluating RTC and trying to import code from Clearcase into Team Concert (CLM 3.0.1 Beta). In this environment, the Clearcase synchronizer license appears assigned.
They also have CLM 3.0 installed.
However, they noticed that in their 3.0 environment, no Clearcase synchronizer license is listed. They have 10 unlocked RTC licenses and 10 free but overall they have 15 assigned and 5 available.
Do they need to install/configure anything additional on their 3.0 server to enable the synchronizer license?
They also have CLM 3.0 installed.
However, they noticed that in their 3.0 environment, no Clearcase synchronizer license is listed. They have 10 unlocked RTC licenses and 10 free but overall they have 15 assigned and 5 available.
Do they need to install/configure anything additional on their 3.0 server to enable the synchronizer license?
5 answers
Posting Geoff's response (from an email exchange on this topic)
Have you tried support? They should be able to help you with these kinds of license questions.
In particular, a set of CC Sync licenses is included with every license install.
One difference in 3.0.1 is that you need to install the "license pack" as well as the server (two separate installs), and then you also have to "activate" the various trial licenses as part of the setup.
Have you tried support? They should be able to help you with these kinds of license questions.
In particular, a set of CC Sync licenses is included with every license install.
One difference in 3.0.1 is that you need to install the "license pack" as well as the server (two separate installs), and then you also have to "activate" the various trial licenses as part of the setup.
Just to clarify, when you say "in their 3.0 environment", are you
referring to the 3.0.1 Beta environment? I assume not, since in the
3.0.1 environment, the CC Sync license appears assigned. BTW, do you
know what they mean by "appears assigned"?
So are they trying to do the import in the 3.0.1 environment or the 3.0
environment? (And if the answer is, "both", then it would be best to
start separate threads ... one for the 3.0.1 license issues and the
other for the 3.0 license issues).
Cheers,
Geoff
On 5/25/2011 2:08 AM, aaakilov wrote:
referring to the 3.0.1 Beta environment? I assume not, since in the
3.0.1 environment, the CC Sync license appears assigned. BTW, do you
know what they mean by "appears assigned"?
So are they trying to do the import in the 3.0.1 environment or the 3.0
environment? (And if the answer is, "both", then it would be best to
start separate threads ... one for the 3.0.1 license issues and the
other for the 3.0 license issues).
Cheers,
Geoff
On 5/25/2011 2:08 AM, aaakilov wrote:
This is actually a question I got from a prospective customer that's
evaluating RTC and trying to import code from Clearcase into Team
Concert (CLM 3.0.1 Beta). In this environment, the Clearcase
synchronizer license appears assigned.
They also have CLM 3.0 installed.
However, they noticed that in their 3.0 environment, no Clearcase
synchronizer license is listed. They have 10 unlocked RTC licenses
and 10 free but overall they have 15 assigned and 5 available.
Do they need to install/configure anything additional on their 3.0
server to enable the synchronizer license?
Geoff,
They are trying to do the import on 3.0. In that environment, their synchronizer license doesn't appear (using a floating license server). They only have developer licenses (no functional licenses) in this environment.
Since they also have the 3.0.1 beta installed, they checked to see if the same issue exists there but the license is there as expected (this env. is not using a floating license server).
They are trying to do the import on 3.0. In that environment, their synchronizer license doesn't appear (using a floating license server). They only have developer licenses (no functional licenses) in this environment.
Since they also have the 3.0.1 beta installed, they checked to see if the same issue exists there but the license is there as expected (this env. is not using a floating license server).
OK, got it, thanks.
I'm guessing it is something strange with the floating license server.
That's something Rational Support should be able to help them with (if
someone else on the forum has experience with that, please chime in).
Note: While they are working with support to figure out how to access
their Synchronizer licenses, they can just assign the cc sync account a
regular Developer license, so they can experiment with setting up
synchronization. Then when they have recovered their Synchronizer
licenses, they can just reassign the cc sync account to one of their
Synchronizer licenses.
Cheers,
Geoff
On 5/27/2011 1:38 AM, aaakilov wrote:
I'm guessing it is something strange with the floating license server.
That's something Rational Support should be able to help them with (if
someone else on the forum has experience with that, please chime in).
Note: While they are working with support to figure out how to access
their Synchronizer licenses, they can just assign the cc sync account a
regular Developer license, so they can experiment with setting up
synchronization. Then when they have recovered their Synchronizer
licenses, they can just reassign the cc sync account to one of their
Synchronizer licenses.
Cheers,
Geoff
On 5/27/2011 1:38 AM, aaakilov wrote:
Geoff,
They are trying to do the import on 3.0. In that environment, their
synchronizer license doesn't appear (using a floating license
server). They only have developer licenses (no functional licenses)
in this environment.
Since they also have the 3.0.1 beta installed, they checked to see if
the same issue exists there but the license is there as expected
(this env. is not using a floating license server).