Hi All,
I am overriding runtime config file using robot manager in which logging mechanism is turned off.
I have an issue in specific user machine. Now i enable logging mechanism in their local machine and restart the runtime. Again it gets overwritten by robot manager config file.
How to overcome this situation and enable logging for debugging.
Thanks,
Vivek.A
@VivekA The easiest way is to assign that user a new RuntimeConfig from Robot Manager. If that is not an option though, a quick way (which is also not recommended by the way as this will prevent the file from being updated by Robot Manager) is to make your changes to the local RuntimeConfig.xml in the %AppData%\Pegasystems folder and then make the file Read-Only. This will prevent a new file from overwriting it from Robot Manager and allow you to collect whatever logs you need. Just be sure to remove the read-only flag when you are finished so that it will be able to acquire the file from Robot Manager.
Similar to packages, updated runtime configs also require ‘deployment’ to the end user. Ensure that the edited config is associated to the correct user or department.