Hi All,
I am looking for the way to start the virtual service on the next available port number at run time. I don't want any developer to hard code the port number in listener step and to avoid the deployment of multiple services with the same port number.
I can write a shell script to get next available number but just to check for any possibility,
I know that recorder will check the port availability before recording. If port is occupied, then recorder will alert you.
Please help.
Thanks.
Yeah right... I guess simple way is (even we do this method)
1. Created port table in shared location (or pulse page) where team has to update the port before they use it , so next person will come to know which port he can use.
2. yeah hard code may not be good practice in listener, so you can create that as a property and assign port in config file..
or
you can assign set of ports to particular teams, so they can play within those ports..
it may not be worth automating this process as it looks like going to take more effort.. any way if you can get other alternative pl let me also know
I did this with my docker solution.. examined the MAR file, and then used a small script to get the next available port number, and mapped the post to the docker instance port from the mar.
I used the docker solution to spin up VSE with one service simulator needed, and shut it down when the test was over.
I did this with my docker solution.. examined the MAR file, and then used a small script to get the next available port number, and mapped the post to the docker instance port from the mar.
I used the docker solution to spin up VSE with one service simulator needed, and shut it down when the test was over.