e2e_appmon Script Considerations

The considerations of creating and deploying the script packages are as follows:
uimpga-ga
The considerations of creating and deploying the script packages are as follows:
  • Script that is recorded on a particular OS can only be deployed on that OS. For example:
    • If recorded on Windows 7, the script does not work on Windows Server 2012 R2 or Windows 8.
    • If recorded on the 64-bit robot, the script can only be deployed on the 64-bit robot.
    • If recorded on OS with IE9, the script can only be deployed on OS with IE9.
    • If recorded on OS, where a dependent file is on the 
      E:\
       drive, the target host must also have an 
      E:\ 
      drive present.
    • If recorded with the NimRecorder 3.9, the target host must also have the NimRecorder 3.9.
  • The absolute path of dependent files is provided while recording the scripts.
  • To create a script package, a profile is created for the scripts that are included in the script package. If there is no profile, a default profile is created with the 
    ROB
     file name in the configuration file after deploying the package.
    As of now, you cannot edit the default settings.
  • A profile and a script cannot have the same name on the target robot, otherwise either the profile name, or the script name is overridden. The robot does not display any warning message while deploying the probe.
  • The dependent files can only be added from the 
    C:\ 
    drive. This process is in line with how current script path is configured in the probe.
  • All the files are copied to the folders according to the robot on which script is recorded, after deploying the package.
  • The robots, on which script package is deployed, must be running the e2e_appmon probe. The 
    Distribution Manager
     deploys the script package without any validation.
  • You cannot deploy only one script from a package (in case the package contains more than one script) to the robot.