Wednesday, August 29, 2012

How to set CITRIX client file security for Load Generator

Problem Statement: During scenario execution, there might be a step where the citrix session will be interacting with local drive for some operations like select a local file to upload. In this case the citrix session on the load generator will be stuck up due to CITRIX client file security dialog. 

Solution: While doing any operations to access local system resources CITRIX gives a pop-up to user to whether to allow the access or not and settings for it (as shown below in the screenshot):


mostly in our session we choose "Full Access / Read Access" and "Never ask me again". So while we replay our scripts on our local machines it runs fine; but this can cause an issue while running a scenario through a load injector (or load generator).

If you are running the scenario through local injector (localhost) then you can manually do the setting while performing the same operation on the application.

If you are running the scenario on a remote injector then you need to login to that injector machine (as admin) and again perform the same operation and provide access to the citrix client (assuming that the injector is running magentproc under your id).

In case of performance center this thing is a bit tricky; in this case what you need to do is to login to the injector machine (as admin) and open the following location:

"(root directory)\Documents and Settings\(username)\Application Data\ICAClient" and open the webica.ini file in a notepad.

by default there will not be any entries in this file, you need to make the following entry after the "[Access]" line:
"GlobalSecurityAccess=405" (this security code is for "Full Access and Never ask me again setting")

Now your webica.ini file should look like this 


please note that you need to make this change for "IUSR_METRO" and "default user" under "Documents and Settings"
Then restart your performance center agent service and run your test; this should enable your transaction to pass on the remote 

No comments:

Post a Comment