Update the common configuration settings to authenticate attended or unattended robot operators and package publish requests in Pega Robot Manager by using the basic method.

The CommonConfig.xml file stores the settings that specify the authentication method and drive the connection between your robotic solution and Robot Manager. For more information about the CommonConfig.xml file, see Common configuration settings.

1. Open the CommonConfig.xml file in a text editor of your choice.
   Typically, the file is in the C:\ProgramData\Pegasystems directory.
2. In the Servers section, for the RobotManager server object, define the following details, depending on your deployment type:

   Choices	Actions
   Attended	Set the enabled attribute to true. Set the authenticationType attribute to Basic or leave empty. Set the baseURL attribute to the Pega Platform URL on which Robot Manager is installed and ensure that the URL ends with prweb. For example, http://www.MyPegaPlatformServer.com/prweb Set the RPA attribute to false.
   Unattended	Set the enabled attribute to true. Set the authenticationType attribute to Basic or leave empty. Set the baseURL attribute to the Pega Platform URL on which Robot Manager is installed and ensure that the URL ends with prweb. For example, http://www.MyPegaPlatformServer.com/prweb Set the RPA attribute to true. Set the robotName attribute to the pattern that you want to use for your robot operator names. For example, to name the robot the same as the machine on which it resides, set robotName to {MachineName}. Set the RPAServiceOperator attribute to the pattern that you want to use for your RPA service operator name. For example, ACME.RPA_Service.

   For example: The following code snippet provides an example configuration when using unattended robots:

   <Server name=”RobotManager” enabled=”true” baseURL=https://MyPegaServer.com/prweb 
   RPA=”true” workgroup=”Savings accounts”
   robotName=”{MachineName}” authenticationType=”Basic” RPAServiceOperator=”ACME.RPA_Service” />

   Note: Do not configure the workgroup parameter in the CommonConfig.xml file. Instead, configure the work group assignment in Robot Manager. For more information, see Robot registration and work group assignment for RPA (unattended) robots.
3. In the Servers section, for the server object whose Server name is IdP, ensure that the enabled attribute is set to false.
4. Save the file.
5. For robotic deployments that include Pega Robot Studio, configure the StudioConfig.xml file by setting the Robotics/PackageServer/baseUrl attribute to use the Pega Robotic Automation Server URL for package deployment.
   StudioConfig.xml contains configuration settings for Pega Robot Studio. For more information, see Studio configuration settings.
6. Configure the RuntimeConfig.xml file by setting the Robotics/PackageServer/baseUrl attribute to use the Pega Robotic Automation Package Server URL for package deployment.
   Important: Edit the RuntimeConfig.xml file only in Robot Manager. Any edits that you make directly in the file by using a text editor are overwritten when Pega Robot Runtime starts. For more information, see Managing robot configuration remotely.