We have a Registry, VSE, Coordinator & simulator running in server (A). I have started the second simulator in a different server(B) and attached to the registry running in server (A). We have some applications & services which will be accessible only from server(B). I like to know is their a way to restrict the test script execution in the second simulator running in server B.
You may be able to use Resource Groups for this. What version of DevTest are you on?
We are using DevTest v10.2.
Will any of the below option work ?
1. Restrict the execution from Stage document ?
2. Create a second coordinator in server(B), attached the second simulator to it, then select the second coordinator while staging the test.
With Resource Groups you can restrict a user to only certain resources.
Here is the documentation link, please review and let me know if this helps.
Resource Groups - DevTest Solutions - 10.2 - CA Technologies Documentation
Server (A) is located in Test environment and Server (B) is located in QA environment. The user needs to develop and run the test scripts first in Test environment by executing the scripts in Server (A) Simulator. Once the application code is promoted to QA, the same script needs to be run against the application from QA environment using Server (B) simulator. So restricting user by Resource Group will not help, as the user will end up in having access in only one environment.
You are right, so you will have to do an internal control to make sure they access Server A in some instances and B in others. It will be dependent on the user to specify the right Simulator in the staging document.
In addition, even if you add a second Coordinator and attach the Simulator to it, you can still access the Simulator on A, so the only other way to truly separate, if not using Resource Groups, is to create a second Registry, then the user can just toggle between the two Registries to do their testing.
As you have different environments, are you using same registry and different simulators? If so. then easiest is to select the specific Simulator in the Staging document.
Both the approaches should work.
If the simulator running on ServerB is selected in the staging document - that is where the testcase would be executed.
premb008 That is my expectation as well.
MarcyNunns I am able to see both the Simulators in the portal, but the same is not listed in the Workstation & Staging document.
I found a document similar to this issue in the below link, but that didn't help as well.
Tech Tips: Not Able to See Registry Monitor Components from Workstation
Looks like the issue was with the port 2015. This port was not open from the Workstation machine. Resolved in SC Ticket 01276326