LoadRunner:How to setup AIX agents with PC controller

pcl2004_27

Description

      Steps required to run AIX agents with a pc controller.


Solution

      How to use AIX as an Agent in a PC Based LoadRunner Controller Scenario
See attached file.


How to use AIX as an Agent in a PC Based LoadRunner Controller Scenario

•        Create a local account on the AIX box.  Use utils such as Mkuser passwd.  *This account will be referred to as runner1 in the rest of the document.
•        Make the user a member of applicable groups, can use smitty command.  We have set the runner1 user to primary group of (engr) and group sets as (engr, perf).
•        Create a home directory for this user as well.  Possibly /export/home/runner1.
•        Install the LoadRunner program to the directory /export/home/tools/lrunner.  You can get the installation files from /net/slwin26/E/Data/LoadrunnerUnixInstall
•        After the installation apply the support pack from Mercury.  This can be located at /net/slwin26/E/Data/LoadrunnerUnixInstall/Patchibm.  The /bin /dat and /include directories contain files that need to be copied into the loadrunner root directory.  Ex  ../patch/bin maps to /export/home/tools/lrunner/bin.  Here is an example of the command you would use for the bin directory:  cp /export/home/patch/bin/* $M_LROOT/bin.
•        Change the ownership of all files and directories in /tools/lrunner to match the local account which will be used for Loadrunner.  The command would be chown –R runner1 /export/home/tools
•        Check the permissions and make sure that runner1 has rwx permissions to the most important files.  We just issued the chmod –R 775 /export/home/tools command to change permissions for all files in the tools directory.
•        Log in to the AIX box as the root.
•        Modify the /etc/hosts file and make sure there is an entry for both the local machine and the machine that will run the LoadRunner controller (Windows).
•        Edit the /etc/environment file and add all path and setenv commands as follows:
o        M_LROOT=/export/home/tools/lrunner
o        LIBPATH=/export/home/tools/lrunner/bin
o        LR_PAGE_SIZE=80
o        DISPLAY=vt100
o        PATH=/export/home/tools/lrunner/bin:/export/home/tools/lrunner/Samples/lrbin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin
•        Modify the /etc/security/limits file.
o        Go to the defaults: section
o        Change the nofiles setting from –1 to 1024
•        Save the file and make sure that runner1 owns the file.  (ls –la)  If not use the chown command to do so.
•        Create a .rhosts file in the home directory for runner1 with the following settings:
o        + +
•        This will allow any host and any user to log into the AIX box through an rsh session.
•        If you want to be more specific add:
o        Controller host name +
o        Agent host name +
•        Save the file and check ownership.  Make sure the runner1 user owns the file.
•        Run a command prompt on the NT controller box.
•        Type the following command:
o        Rsh unixhostname –l runner1 –n env
•        Verify the environment settings on the AIX box and make sure that the settings described above in the environment file are listed.
o        You may have to log in as runner1 on the AIX box (rlogin localhost –l runner1) before issuing the rsh command from NT.  For first time login it will prompt you to change your password.  After doing this try the Rsh command on NT again.
•        Once the rsh session succeeds from the NT controller, you are ready to set up your Loadrunner scenario.
•        First make a copy of your loadrunner script and save it to a non long name space directory on your controller box.
•        Open up the controller.
•        Create a new scenario.
•        Go to the scripts tab and add your script using the shortened directory.
•        Next go to the hosts tab and add a new host.  The name will be the name of your unix box.   ex. slaix10
o        Make sure and change the platform to Unix.
•        Once the host is added, right click on the host and edit the details of the host.
•        Change the Temp directory as follows:

•        Click on the Unix Environment tab and set the login as parameter to runner1.  See the following screen for more information:

•        Try to connect to the host.  See if the host goes to a ready state, it should.  
•        Next create the virtual users and then initialize them.  They should go to a ready state.
•        Make sure in the run-time setting to mark the Analog mode option.  This is required by all Unix agents.
  
•        If there are any errors on the controller you can put the controller in Debug mode by going to help and about Loadrunner and then position your mouse anywhere on the help screen and right-click once, left-click twice and right-click three times to put the controller in Debug mode.  You should see a dialog box telling you it has been done.  This will give you additional information if the script fails for any reason.