Forum Discussion
7 Replies
- marinFrequent ContributorHello Armands,
we have similar envoronment set up like this:
- TestComplete with node locked license on my development machine (physical)
- TestExecute on a virtual machine in the same network
- TestComplete license manager on another virtual machine in the same network
VM with TestExecute does not have internet access, but the VM with license manager does (must have for licensing with SmartBear license server).
The VM with TestExecute has access to VM with license manager (same network) - in the settings for TextExecute (on license activation) you will need to specify the VM where license manager is running.
This works without problems for us and I hope that this will help you set up your environment.
Regards,
Marin - ArmandsBrunsFrequent ContributorHi Marin,
Thanks for your response,
Does this means that I can active my TestExecute on virtual machine and run on it (VM has only requirment the access to intertnet)
Best regards
Armands - marinFrequent ContributorHello Armands,
correct, you can activate the TestExcute license on the VM where it is installed and running.
Regards,
Marin - ArmandsBrunsFrequent ContributorHi Marin,
Which version you use?
Because there are differences:
The License Manager PC for TestExecute depends on how you got TestExecute:
If you have TestExecute as part of the TestComplete trial or as part of the TestComplete Enterprise or Universal edition version 8.50 or earlier:
In case of the TestComplete Node-Locked license, the License Manager PC for TestExecute instances is the computer on which TestComplete is installed.
In case of the TestComplete Floating User license, the License Manager PC for TestExecute instances coincides with TestComplete’s License Manager PC.
If you purchased TestExecute as a separate product or if you got it as part of the TestComplete Enterprise edition version 8.60 or later, the License Manager PC for TestExecute instances is the computer where the TestExecute license is activated.
Best regards
Armands - marinFrequent ContributorHello Armands,
we are using the latest TestComplete Enterprise 9.30.3373.7 with corresponding TestExecute.
In our environment the scenario with TestExecute and license manager service being on different machines works without issues.
As described here, we have HASP Sentinel licensing service as standalone utility and not on the machine where TestExecute is installed and running.
Not sure if there are any limitations or specifics with trial versions.
Regards,
Marin - ArmandsBrunsFrequent ContributorHi Marin,
As I understand, I can install the License Manager as a standalone utility and activate commercial license of TestExecute on the same machine where was activate a commercial license of TestComplete.
Regards
Armands - marinFrequent ContributorHello Armands,
I guess so...
Sentinel license service is installed with TestComplete as well - see in Windows services.
On my local machine it is called "Sentinel Local License Manager" and points to C:\Windows\system32\hasplms.exe.
On the machine where we have standalone license manager service installed (for TestExecute only) it is called "Sentinel HASP License Manager" -> points to same .exe in its system32 though.
Here you can access the admin page for licensing service (on the machine where your TestComplete is already installed):
http://localhost:1947/_int_/ACC_help_index.html
Look for tab "Access from remote clients"...
If you intend to manage your TestExecute license from the machine where your TestComplete is installed, it might be that you can indeed manage it through (already through TestComplete installed) "Sentinel Local License Manager" -> but - although I would expect it to be like that - I can not confirm this as we have slightly different environment (as descirbed in previous posts).
I'm not sure why would you install TestExecute and TestComplete on the same machine? The reason we wanted to have these two seprated is the fact that TestExecute should be able to run independently (mostly in the night) from TestComplete (which is on my local development machine) - which would certainly not run at night :-).
So we decided that best approach is to have these two separated. Having decided that, the question of license service emerged - thus we needed to install the licensing service on a different machine which is running 24/7 and thus always provides access to licensing server for TextExecute.
Hope this helps.
Regards,
Marin