Service Virtualization

hello - I have two questions around config files which will help us a lot in case if resolved..

1.  Different configs -- We have multiple lisa server configs and multiple lisa servers as well.. every virtual service developed needs to be deployed into different lisa servers with different config.. at the moment we need to change the registry from workstation and deploy in each and change back the registry to other servers .. 

Do we have any better process for this please ? can we define any logic in config file or model to deploy the service across the different environments ?

2. Can me change the VSM name using lisa property .. like usually we use property within double braces to represent a property.. 

reason is I have 5 config in each project and one VSM.  so whenever I deploy the VSM in same environment with different config it will be good display the VSM name in server console something like "VSMName_ConfigName"..

I tried this option which did not work.. i.e., define a key in config property and value stored under this property is name of the config.. 

now, modified the VSM name to VSMname_{{the key name under config}} .. but this did work.. when it deployed to console it shows the same name rather than replace the value for {{the key name under config}}

Melanie_Giuliani

looks like no one has come across this query.. could you please help to get some answer  if possible.. 

Koustubh.Warty - do you know who we could direct this question to, to try and get DevTestUser an answer?

Hi,

 I have an alternate solutions:

Q1:

Connect all VSE's in different Environments to single Registry While Deploying VSM select respective VSE server and config file,You service will be deployed on expected machine with respective config file

Q2:

While Deploying we can see Name in above screenshot BaseImage_vsm_TEST,by renaming it to "VSMName_ConfigName",same u can see in console

Same case if you want to run Testsuites with different config file i suggest use LISA INVOKE,since u are expecting VSM to be deployed try above option.

Thanks

Jaya

Q1:  This will not be good idea of connecting all other server on same registry.. because if one registry is down then everything will go down.

Q2:  Yeah currently we are doing that but this leads to typos.. every time we need to manually change this and remember what we had set earlier.. else need to refer back in console 

Hi DevTestUser,

I have few questions that I need in order ti help you:

1. Why you need different Config files? Because if you connect to different LISA Environment then you don't need to be bothered about the Config files. Just I have doubt about this, let me know what are details you are keeping in the different Config files else we can eliminate this one.

2. If we eliminate the Config files, then we don't need to be bothered about the renaming the VSE's renaming them.

Let me know about the above questions as I'm kind of confused.

Thanks,

Abhishek

Because different config has different details, we deploy service on different ports, queues etc., 

Another option you have that gives you flexibility in terms of deployment will be to use CLI tools like VSE Manager and Make Mar to build the mar files and deploy to multiple target VSE's programmatically based on rules defined by you. You can control and keep track of where you are deploying. More information on these utilities at the links given below.

https://docops.ca.com/devtest-solutions/9-5/en/using/using-ca-service-virtualization/vse-commands/vse-manager-command-manage-virtual-service-environments

https://docops.ca.com/devtest-solutions/9-5/en/using/using-ca-application-test/using-devtest-workstation-with-ca-application-test/working-with-model-archives-mars/make-mar-utility

Thanks,

Surya.

Thanks .. it may not be much helpful in my case but can be used based on need..

it would be good in future if there is way to define the registry details and authentication inside config file and can be deployed from one registry to different registries.