Jump to content
WAPT Forum

Server Port not Dynamic

Recommended Posts



WAPT lets you specify a variable for the Server

But it does not let you specify a variable for the Port.


The scenario I am trying to support is


Logon to initial URL

Logon load balance occurs - via a REDIRECT contained within a link.

This link contains a different URL which containis a different Server:Port .


We can capture the Server, and the Port, from the REDIRECT.

We can change the Server property to be "$Var(RLink)" - where RLink is the Server name from the REDIRECT URL

But - we cannot change the Port property to be from a variable - which is also populated from the REDIRECT URL


If the Ports for the various Servers involved are different - then we cannot use WAPT to replay traffic by going via the logon load balancing mechanism


Is there a way to specify a variable that can be used to determine the PORT for the Server - at runtime?

This would also provide WAPT profile portability between environments - where the Server and Port ranges can often be different.



Share this post

Link to post
Share on other sites



Can the Server Port parameter be changed to take its value from a Variable?

The test scenario I cannot complete at the moment is:


We login to an initial fixed URL

Logon load balancing then occurs, and we receive a REDIRECT via a URL link.

We use Search variables to grab the SERVER and the PORT from the REDIRECT link.

One subsequent pages - we replace the originally captured SERVER value with the Search variable - so the SERVER value is dynamically set at runtime.

This way we correctly move to the server we have been redirected to by the logon load balance


We also need to set the PORT value in the same fashion.

The reason we need to set the PORT value in the same fashion - is due to the PORT number being different for different SERVERs.

At present - the PORT value at runtime has to remain the same for all traffic for the duration of each session.

This means all SERVERs have to have the same PORT value.

When one SERVER has a different PORT value than the others - then each WAPT session that is load balanced to this server will fail.



Share this post

Link to post
Share on other sites

Thanks Sergei.

So the latest build is "WAPTPro3.5.zip 31-Oct-2014 02:20"


I have WAPT Pro 3.1 installed - which was installed in March 2014.


Do I uninstall 3.1 first, then execute "WAPTPro3.5.exe" to install the latest build?

Share this post

Link to post
Share on other sites

You can leave WAPT Pro 3.1 installation but in this case you can face some problems.

So I recommend you to uninstall 3.1 first.

Share this post

Link to post
Share on other sites

Uninstalled 3.1

Installed 3.5

Opened up existing scenario/profile - got converted from 3.1 to 3.5

Made the change for Server Port to be specified by a variable.

And the Initial test looks good/passed - successfully worked against 2 servers with .


Thank you Sergei

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...