Adding .jar files to a Silk Performer project, classpaths within the Active Profile Remote Java settings are not updated
Within the Silk Performer Active Profile Java settings (SILK PERFORMER | SETTINGS | ACTIVE PROFILE | JAVA), two different tabs are provided which will display the class paths of .jar files which have been added to the Silk Performer project, these are the 'General' and 'Remote' tabs.
By default, when an addition of a .jar file has been made to the project, both the class path's within the 'General' and 'Remote' settings are updated, when the 'Use different settings for remote agents' option has been unchecked within SILK PERFORMER | SETTINGS | ACTIVE PROFILE | JAVA | REMOTE.
Refer to the following screenshots:
The reason why the Remote Java settings, as well as the General settings, class paths are updated when a .jar file has been added to the Silk Performer Project, is down to the fact that when the 'Use different settings for remote agents' option has been disabled, the same settings (.jar files) are applied to both local and remote machines.
If the 'Use different settings for remote agents' option is enabled prior to the addition of a .jar file to the Silk Performer project, then different settings will be applied to the remote agent in comparison to that of the local machine, thus displaying the behaviour that the class paths have not been successfully added to the Remote Java settings within Silk Performer | Settings | Active Profile | Java.